The deskilling pattern that hollowed out Western defense manufacturing is now repeating in software engineering, on the same timeline.
Key Takeaways
Western defense industries optimized for minimum cost with zero surge capacity, leaving them unable to scale production when crisis hit.
Software engineering is following the identical structural path: skills erode when demand shifts to higher-level abstractions and AI-assisted output.
Just-in-time knowledge works until it doesn’t. Skills that are never exercised cannot be lazy-loaded back quickly when urgently needed.
The core risk is not that tools change but that institutional capacity to work without them collapses silently over years.
Hacker News Comment Review
Commenters split on whether this is a new problem: one framed COBOL as a 40-year precedent, arguing skill loss is a permanent cost of progress that gets “lazy-loaded back at significant cost” when needed.
The sharpest pushback reframed the article’s core claim as a systems-design problem, not a skills problem: “Efficiency is the reciprocal of resilience” captured the tradeoff more precisely than the manufacturing analogy.
The open question left unresolved in comments: whether the current erosion is a tooling artifact or an incentive and training failure, with no consensus reached.
Notable Comments
@bsder: Flagged the surge-capacity framing as quotable; tied it to Stross’s systems-resilience maxim for broader application.
@Meirambek_VIDI: Raised whether the root cause is tooling or engineer training incentives, a distinction the source preview does not resolve.