Comment by tonestonestones
6 months ago
In some way, software development is going the way hardware development went years ago. The engineers built tools and modules that put most of them out of work. Who designs amps or discrete circuits these days? Once you design a piece of hardware that works well, it can be re-used ad-infinitum, and most hardware today is really firmware running on microcontrollers. So it is a natural evolution that software is becoming automated. Unfortunate, but also an opportunity to do more interesting things. It is the managers that need to be replaced unless they can see further than the tecchies, and I have known some that do, usually they are ex-tecchies.
> The engineers built tools and modules that put most of them out of work.
Yes, but no. I'm in hardware. I deal with hardware engineers. This part of the industry is alive and well. You might not see it, but it's there.
> Once you design a piece of hardware that works well, it can be re-used ad-infinitum, and most hardware today is really firmware running on microcontrollers.
Yes to the first part, it's just like code. Write once, then run it perpetually. Except that isn't really the case. There are still jobs for maintaining COBOL systems. Likewise, legacy hardware needs to be replaced, improved, or repaired. Old companies die, new ones swoop in and capture market share. My employer is the only manufacturer I know of for a legacy system component. They have a captive market because no one else wants to take the two weeks in CAD, and phone time with the contract manufacturers. This kind of thing is everywhere.
> So it is a natural evolution that software is becoming automated.
Again, yes, but no. We automate things as a matter of course. We are engineers. This doesn't mean fewer jobs, it means a shifting job market. IE loom operator vs hand weaver.