Programming Still Sucks

· ai · Source ↗

TLDR

  • Tech work was always chaotic and unglamorous; AI isn’t killing programming jobs – cost-cutting greed is, and it abolished the apprenticeship pipeline in the process.

Key Takeaways

  • The junior engineer hiring collapse is framed as an apprenticeship crisis: juniors weren’t valuable for output, but for becoming the seniors who carry institutional knowledge.
  • “Sara” archetype – mid-career engineers holding critical undocumented systems together via USB sticks and tribal knowledge – represents infrastructure risk that layoff spreadsheets cannot see.
  • CEOs returning from offsite demos (agents writing features in 14 minutes) drove 30% engineering headcount cuts before validating the premise; Goodhart’s Law ate every metric handed to non-engineers.
  • DORA metrics signal deployment stability degrades when tooling is added faster than judgment; the post names this as a known, ignored warning.
  • The author implicates engineering leaders directly: they signed layoff lists knowing the consequences, rationalizing visa, mortgage, and “fix it next quarter” logic.

Hacker News Comment Review

  • Commenters broadly praised the writing quality as rare and distinctly human – one noted finishing the whole piece without detecting AI co-authorship, a low bar that landed as a sharp observation.
  • Dissent exists: a 40-year programmer pushed back hard, arguing programming remains joyful for most, juniors are still hired in the hundreds of thousands annually, and the piece adds no actionable analysis.
  • A notable reply reframed the “it used to be good” nostalgia: the technology was never clean, you just stopped noticing the dysfunction – the industry was always bad to some, now it’s bad to everyone.

Notable Comments

  • @Waterluvian: Raises the productivity-capture problem – engineers work the same 40 hours, AI productivity gains flow entirely to employers, none to workers.

Original | Discuss on HN