The 'Hidden' Costs of Great Abstractions
High-level software abstractions and AI tools like LLMs are making it easier than ever to build applications, but many engineers argue this progress is eroding deep technical understanding, code quality, and long‑term reliability. Commenters connect this trend to a broader shift in the industry: firms prioritize speed, cost-cutting, and “good enough” solutions over craftsmanship, leaving specialists and older developers struggling in a tighter, more commoditized job market. Some see this as a symptom of a distorted economy where efficiency gains don’t translate into better lives for workers, warning that over-reliance on opaque tools may eventually backfire when complex systems fail.
Role of Abstraction and Its Costs
- Many argue modern abstractions (frameworks, LLMs, cloud, no-code) let more people build things faster, which is socially good.
- Others say “great” abstractions hide too much: fewer people understand underlying systems, leading to bloat, inefficiency, race conditions, and hard-to-debug failures.
- Several contrast earlier eras where abstraction was temporary (peeled away near hardware) with today’s permanent, thick stacks.
LLMs, Productivity, and Jobs
- Strong concern that LLMs + agentic coding reduce demand for traditional dev labor, especially mid-level roles.
- Some say business fundamentals have shifted: companies care more about shipping quickly and cheaply than about elegance or deep expertise.
- A minority argues that abstractions always change fundamentals rather than eliminate them; future devs will focus more on design, product thinking, and verification of AI output.
- Disagreement on whether LLMs are “just another abstraction”: some see them as uniquely non-deterministic and hard to reason about compared to compilers or runtimes.
Devaluation of Deep Expertise
- Multiple comments lament that understanding internals, concurrency, and architecture is now seen as a liability when the incentive is “close Jira tickets fast.”
- Observations of anti‑intellectualism: foundational topics (runtime vs compile time, concurrency safety, messaging, etc.) are dismissed as unnecessary gatekeeping.
- Others report domains (games, embedded, some enterprise) where deep knowledge is still valued and required.
Hiring, Resume Fraud, and Gatekeeping
- Several unemployed or underemployed devs share long job searches, especially mid‑career or with disabilities.
- Concerns that widespread GenAI-crafted resumes create “spam,” making online applications nearly useless.
- Some advocate a return to higher-touch intermediaries (staffing firms, “agents”) to verify candidates.
- Advice appears to focus on better self‑presentation, coaching, and possibly career pivots (QA, security, even outside tech).
Broader Economic and Social Anxiety
- Worry that automation’s benefits are captured by capital while humans still must work for basic survival.
- Fears about Western dev jobs being offshored or compressed, especially for older engineers and for Gen Z trying to enter.
- A mix of resignation, stoic coping, and calls to “not go quietly” against erosion of craft and working conditions.