A question on Hacker News is capturing a sentiment that is spreading through the software development community: if AI can write all the code, what happens to the people who spent decades learning to write it?
The anxiety underneath the question
The poster describes a specific kind of despair. They have spent years in school and on the job building skills they are passionate about. They get energy from writing code. The people running the frontier AI labs are telling them that soon all code will be written by models. The logical conclusion, from their perspective, is that the skill they built their career on is becoming worthless, and the economic system that rewarded that skill is about to stop working.
The poster does not believe in universal basic income as a solution. They argue that the world has never worked that way, that humans do not have equal capabilities or resources, and that without the motivation provided by work, cognitive skills will decline and people will become dependent on the machines. The fear is not just about economics. It is about identity, purpose, and what happens to people when the thing they are good at no longer matters.
What the replies say
The post received ten comments, which suggests the question resonated. Without reading every reply, the general shape of optimistic responses in these discussions tends to follow a few patterns. Some argue that software engineering is about much more than coding, that understanding systems, communicating with stakeholders, and making architectural decisions are human skills that AI cannot replace. Others point out that every previous technological disruption, from assembly language to high-level languages to frameworks, was supposed to eliminate程序员 and instead created more work.
The counterargument to the optimism is that this time is different because the tool being automated is the tool that does the automating. Previous disruptions replaced manual labor with machines. This disruption replaces cognitive labor with systems that can improve themselves. The feedback loop is tighter and the pace of improvement is faster than anything in previous history.
What is actually happening to developer jobs
The honest answer is that the data is mixed. Some companies are hiring fewer junior developers because AI tools handle the simpler tasks that juniors used to learn on. Other companies are hiring more developers because AI tools make them more productive and the demand for software has grown. The net effect depends on the industry, the company, and the specific role.
What is clear is that the nature of the work is changing. Developers who spend their time writing boilerplate code, converting specifications into implementations, or debugging routine issues are seeing those tasks get faster with AI assistance. Developers who spend their time understanding problems, designing systems, and making decisions about tradeoffs are finding that AI tools amplify their output rather than replace it.
The distinction is not about skill level. It is about what the work involves. A senior developer who spends most of their time in meetings and architectural reviews may find that AI tools reduce the time they spend coding without reducing their value. A developer who spends most of their time writing code to a specification may find that the specification gets implemented faster, with fewer humans needed to do it.
What keeps people motivated
The developers who remain optimistic tend to share a few characteristics. They enjoy the problem-solving aspect of the work more than the coding itself. They have found roles where their judgment matters more than their output. They have adapted their workflows to use AI tools as force multipliers rather than viewing them as replacements. And they have stopped measuring their value by the number of lines they write.
The poster's despair is understandable and shared by many. The tools are changing faster than the career paths can adapt. The economic model that rewarded coding skill is shifting in real time. But the work of building software, understanding problems, making decisions, and creating systems that serve human needs is not going away. The part that is going away is the assumption that writing code is the same thing as doing that work. For developers who can make that distinction, there is still a career. For those who cannot, the transition will be harder.