A software engineer reflects on AI-driven workplace shifts, eroded craft satisfaction, and whether the tech industry still matches their values.
Key Takeaways
The post frames AI adoption not as a productivity story but as a values rupture for engineers who built careers around deliberate, craft-oriented work.
“Loss of an ideal” points to disillusionment with how engineering culture is shifting, not just with specific tools or employers.
Quitting is presented as a principled response to misalignment, not burnout in the classical sense.
Silent dissent is identified as a real dynamic: pushback on AI use carries social cost, so most engineers absorb the friction without voicing it.
Hacker News Comment Review
Commenters broadly agree that code review was always about institutional knowledge transfer, not gate-keeping; AI-generated mass submissions destroy that loop by optimizing only the merge step.
A recurring read: AI adoption is exposing that many orgs historically rewarded the appearance of productivity over actual output, and are now accelerating that mismatch at scale.
Engineers split sharply on craft loss: some report real velocity gains but describe the work as “bland”; others argue that code is fundamentally human-to-human communication, and AI-generated code breaks that contract regardless of correctness.
Notable Comments
@erentz: “what has always mattered has been the appearance of work, not results” – argues AI is accelerating a pre-existing org failure mode, not creating a new one.
@xtracto: frames programming languages as a communication medium between people, not just machine instructions; mass AI code generation breaks that social layer.
@zby: notes consequential AI failures being ignored by companies, questions whether competitive pressure will route around orgs that skip failure-mode accounting.
