AI isn't going to kill the software industry

Impact of AI on Software Jobs and Industry

  • Many argue AI won’t “kill” software but will make it cheaper, unlocking previously uneconomical projects (Jevons paradox: more efficiency → more demand → more software).
  • Others counter that companies have finite useful projects and hit growth plateaus; at some point faster development means fewer devs needed, not more.
  • Several expect the kind of work to change: fewer boilerplate coders, more people doing architecture, integration, product thinking, and “AI wrangling.”

Changing Roles and Skills

  • Debate over whether future work is still “software engineering” or becomes something closer to technical product management / configuration of AI agents.
  • Concern that tools optimized for mid/senior devs will further squeeze entry-level roles and widen generational divides between “pre-AI” and “AI-native” developers.
  • Some see AI as the “new compiler” or “fancy REPL” that still requires deep technical understanding; others imagine a world where non-programmers effectively “operate” software like elevator users.

Productivity, Quality, and Tech Debt

  • Many report real productivity gains for tasks like boilerplate, tests, glue code, refactors, scripts, and learning new tech.
  • Others find current tools overrated or unhelpful, especially in large legacy codebases or highly constrained domains (e.g., safety-critical embedded systems).
  • Worries that easier code generation will encourage more tech debt and sloppier, harder-to-maintain systems, especially when business incentives favor speed.
  • Some stress ongoing need for maintenance and domain-specific reliability; layoffs that ignore this lead to bit rot and eventual failures.

Economics, Wages, and Power

  • Some fear AI will be used by executives to demand 5x output without higher pay, pushing down salaries and further “feudalizing” tech work.
  • Counterpoint: productivity tools historically expand markets and can increase total high-skill employment, though distribution is uneven.
  • Analogies (horses, shoemakers, elevator operators, radiologists) are used both to argue “this time isn’t different” and to argue that specialized, well-paid roles can still be hollowed out even as the broader industry grows.

Learning, Tools, and Resources

  • Suggestions include practical books on prompt/AI engineering and hands-on projects like reimplementing small GPTs.
  • Some doubt books can keep pace with rapid change and prefer experimentation and tool-building to understand the ecosystem.