A software engineer argues LLMs should be used like editors for system design plans, not as replacements for skilled developers, to avoid long-term workforce and technical debt problems.

What happened: An experienced software engineer reflected on how a colleague was using Claude (an AI assistant) to build code from detailed design documents—documents that closely resembled the formal requirements specifications used in traditional engineering decades ago. The engineer observed that LLMs are being positioned to automate work across multiple levels of system development, from architecture review to junior developer tasks.

Why it matters: The engineer argues that LLMs are best suited to ensure consistency and catch missing elements in system designs—work similar to an editor's role—because they excel at "ensuring normalcy." Using LLMs to make major technical decisions (like team assignments) or to build critical systems directly risks creating undetected technical debt and losing the ability to develop skilled engineers who learn by doing. The concern is not that LLMs cannot perform these tasks, but that outsourcing core development work damages long-term organizational capability.

What to watch: The engineer expresses skepticism that traditional engineering practices will be restored in modern workplaces, expecting instead that cost-focused leadership will prioritize short-term savings over workforce viability—a dynamic the author suggests is driven by leaders who may move to other roles before long-term consequences appear.