4 ms·
That's just a disingenuous distortion of semantics. You're deliberately ignoring the key difference between skill-based, white-collar jobs and unskilled, blue-c
by CodeMage 7y ago
That's just a disingenuous distortion of semantics. You're deliberately ignoring the key difference between skill-based, white-collar jobs and unskilled, blue-collar jobs. The former are not "destroyed" by productivity, as you put it. They change what the workers have to do, but the workers are, for the most part, able to adapt.
None of the advances in software development have eliminated software development. Hell, there are still job openings for COBOL developers. CI hasn't resulted in a whole swaths of people suddenly out of work because they were running tests by hand and now there's nothing else they can do.
- bin0 7y agoHe may not have phrased it perfectly, but his point is good. Picture this: you are hired to do a contract job. The tooling today is arguably better than 20 years ago. You bill by the hour, and take fewer hours. Now, extend that to salaried positions. There is a certain amount of work that must happen. Tooling improves, devs become more idle, management consultant fires one (over time). This has been somewhat negated only because the role of computers has been growing quickly and outpacing the growth in efficiency. That will change at some point. As you said, there won't be a case where swathes of people are suddenly out of work, it will be gradual. A guy I know is an economist and does consulting for factories to optimize production. He has talked about how some areas these days have removed large groups of humans and replaced them with single humans observing machines. Eventually, development could reach a similar place.