Author overlooks three important things.<p>First, with amount of software engineers doubling every ~5 years, there is mostly a shortage in software developers <i>with experience</i>. Someone has to teach. Someone has to steer, make decisions based on knowledge, someone has to design architectures, know what coupling matters, what patterns apply, what type of solutions will haunt you later on, etc. etc. etc. No junior can do these things, because the juniors lack the experience of failing several times or maintaining or replacing legacy over years.<p>Secondly, software development is about so much more than writing code. In fact, I spend least of my time typing in code. If your job really is <i>typing code that others told you exactly how to write</i>, then yes, fear for your job. Not because of copilot or better IDEs but because what you do is easily automated away. If people doubt me, I urge them to look at their git-log over the last weeks. I daresay that most will hardly write/edit more than 100 lines of code a day. That's less than 5 lines per minute.<p>Nearly all software development is about understanding the domain and applying software to solve problems in that domain. About researching what problems are most urgent and what solutions have which tradeoffs. Which patterns apply, how to decouple, where to draw lines, how to keep the software agile and maintainable over decades, and so on. Hell, even "where to put my code" is a hard problem that copilot and IDEs fail miserably at.<p>Thirdly, the no-code movement is a forever-september thing. It has a niche, but that niche is not as big as the no-code salesmen would like you to believe. I've seen "lo-code" come and go for decades now. Every time it promised to take over all the software development only to carve out a niche and be very good only there. More practially: most such no/lo-code systems lack a lot of essential paradigms (source-control, accountability, copyability, testability). But they are either far too generic and therefore just as complex and hard to manage as "real software", or they have a specific niche and shine there! (but only there).<p>So no. Software engineers, especially those that have been in the trade for years (even more when decades) are in high demand and will remain so. Tools won't replace them. If anything, tools (which are build and maintained by those developers) only increase the demand.