3 ms·
I remember people saying that, too. In 1980. It really isn't true, and the reasons why it isn't true have been known for a long time, and it will never be tru
by jerf 16y ago
I remember people saying that, too.
In 1980.
It really isn't true, and the reasons why it isn't true have been known for a long time, and it will never be true, and it is this: A (good) programmer is always prototyping. Virtually by definition, you are doing something that hasn't been done before. If it had been done before, you would buy it or download it, it would be a component, and then you would move on to the part of the problem that hasn't been done before.
It is not true that programming is moving towards a model where you just grab components off the shelf and wire them together. Or if it was true, it has happened, it is in the past, it isn't "becoming" true. All the components mean is that you no longer have to research the best way to handle images, and you get a lot farther before hitting the unsolved part of your problem... but it's only the unsolved part of the problem that is interesting. There's no money in solving solved problems. (Well, that's not entirely true, but this is a comment reply, not an exhaustive description of all programming niches.) The unsolved problem is always the focus and pretty much by definition there will always be more unsolved problems.
If you aren't writing much code and you really, truly are just wiring bits together, it is time to either learn how to write metacode that wires the bits together for you and start wiring much, much faster, or to desperately cast about for a new skillset because you are easily replaceable (or possibly just discardable) and you really need to change that as quickly as you can!
- devmonk 16y agoDevelopers are using more and more code that has already been written. Sure we still code, but if you were coding in 1980 (like I was), then you know what I mean. I'm with you and the author that the non-technical customer is not going to be able to move the legos around on the screen until they have their working webapp. I've been a part of projects that promised those types of things, and they were failures for the most part. But, the trend is to have more and more complicated pieces that the developer puts together. The developer feels as if he/she has really done something significant, but what they did technically was more brainless than what a game programmer wrote in assembly in the early eighties, for sure. If developers need to know less and less about what is really going on, sure maybe they will still be called developers, but they'll be closer in function to the guy making your big mac. It won't happen overnight, but just because it hasn't happened yet and may not happen during our lifetimes doesn't mean it won't.