- 133comments
- 15comments
- 235comments
- 27comments
- 23comments
- 66comments
- 7comments
- 221comments
- 39comments
- 427comments
- 5comments
- 67comments
- 81comments
- 2comments
- 188comments
- 1comments
- 10comments
- 2comments
- 165comments
- 131comments
- 151comments
- 153comments
- 84comments
- 29comments
- 56comments
- 21comments
- 28comments
- 2comments
- 453comments
- 19comments
This article does a whole lot of "they" and "we" with which I strongly disagree.
Well yes the internet was here to stay, but if you used that line of thinking to invest heavily in the DotCom sector at that time you were in for a rude awakening.
There’s a major difference between rejecting a technology and rejecting how it’s being packaged and sold.
Getting rid of software engineers could be the Doorman Fallacy[1]. How much of the job is writing new code? A lot of it is solve problems/maintenance, improvements, integrations with other systems, update existing implementation, delivery automation support.
[1]: https://en.wikipedia.org/wiki/Doorman_fallacy
Well (human) written article, and I do sense all of this around me. Rather than go into denial, I think it would help everyone to discuss the core points: SWE is no longer a differentiated role that could gatekeep the way it did.
This means the newer SWEs have to now get some real-world connection / get their hands literally dirty to be valuable.