> Today, I type "npm install json2csv" and I'm done.
You have to do a little bit more: You have to search for it and decide which of the n converters you will use (licence, other dependecies, ..)
But I get your point.
You have to do a little bit more: You have to search for it and decide which of the n converters you will use (licence, other dependecies, ..)
But I get your point.
My parent was an electrical engineer. While their skillset was varied, and heavily weighted towards physics and math, their day job was mostly about knowing how to pick parts out of a catalogue, which catalogue to use when, and maintaining good relations with the suppliers behind those catalogues. I always saw this as a weird disjunction.
Until now.
I've just realized that while my core skillset is in math, logic, computer science, and system design, I do spend a lot more of my time researching repositories, packages, licenses, etc, than actually coding. But with the new perspective your comment gave me, I finally saw that as totally in line with other, older engineering disciplines.
So, to address the original point of this thread, it seems as if programming has finally evolved into a semi-mature engineering discipline, wherein our ability to gauge the quality of existing supplies is more important than our ability to produce new supplies.