Software engineering may no longer be a lifetime career

Original Article ↗ Hacker News Discussion ↗

Software engineers are debating whether advances in AI and code-generating tools will turn programming into a short-lived career, more like professional sports than traditional knowledge work. Many argue that while LLMs can automate large amounts of “typing code,” the enduring value is in problem framing, system design, domain expertise and judgment — skills that are harder to replace but may be needed in far smaller numbers. Others worry that companies will use AI and offshoring to shrink engineering headcount, hollow out junior roles and depress wages, with uncertain prospects for retraining or new high-quality jobs.

Scope of the change: tool vs. job replacement

  • Many see AI coding tools as “power tools” that reduce typing but don’t replace software creation itself; others argue this is the first real threat to generalist software careers.
  • Two broad futures are sketched:
    • Fewer developers doing vastly more (company keeps staff, does 10x work).
    • Many developers replaced (company fires 90%, keeps 10 “pilot” engineers + AI).

What software engineers actually do

  • Several claim only a small fraction of their time is raw coding; most is:
    • Understanding problems and domains.
    • Clarifying requirements, design, and trade‑offs.
    • Coordinating with stakeholders, testing, reviews, docs.
  • Counterpoint: for juniors and many “CRUD” developers, a much larger share is straightforward coding, making them more exposed.

AI, cognition, and skill atrophy

  • Some worry heavy AI use replaces rather than augments reasoning, leading to:
    • Atrophy of problem‑solving and technical depth.
    • A generation that can “vibe code” but not understand systems.
  • Others argue:
    • You can still learn a lot by supervising AI and tackling more varied tasks.
    • The key distinction is augmenting vs outsourcing thinking.

Determinism, quality, and “AI slop”

  • Many reject the “LLM = compiler” analogy:
    • Compilers are deterministic, spec‑preserving, and auditable; LLMs are probabilistic, underspecified, and need review.
  • Experience with AI‑generated code is mixed:
    • Some report huge productivity gains on routine work and refactoring.
    • Others see endless “reorganized mess,” hallucinated patterns, and fragile agentic systems.
  • Concern about “single‑use plastic software”: cheap, disposable, low‑quality code proliferating, later expensive to maintain.

Labor markets, juniors, and career longevity

  • Thread notes existing trends: ageism, offshoring, COVID over‑hiring and layoffs, and now AI as an executive pretext for cuts.
  • Widespread fear that:
    • Junior hiring collapses (“AI can do junior work”), breaking the pipeline to future seniors.
    • Many white‑collar roles (dev, support, basic analysis) are compressed or offshored.
  • Some think the sweet spot shifts to:
    • Domain experts + basic programming + AI orchestration.
    • Fewer “pure” software generalists, more hybrid roles.

Retraining, inequality, and society

  • Skepticism that “people will just retrain”:
    • Unclear what new mass professions would be both AI‑ and offshoring‑resistant.
    • Local trades (plumbing, construction, healthcare) have limited capacity and are themselves being automated at the margins.
  • Recurrent theme: if AI really does large‑scale white‑collar replacement, outcomes depend more on political choices (redistribution, safety nets, labor power) than on technology alone.