Software Engineering Career

Summary

A recurring undercurrent in Mr. Nayak’s catalog: what happens to software engineering as a profession when AI can generate most of the code? Sources range from philosophical (is it still a lifetime career?) to personal (laid off by Atlassian) to practical (reading code, interview prep tools, the vibe coding debate). The picture is nuanced — AI doesn’t eliminate the engineer, but it reshapes what “being a good engineer” means. This week’s vibe coding discussion added another data point: experienced developers may rationally opt out of AI-assisted workflows not from technophobia, but from a clear-eyed cost-benefit read.

Key Sources

W22 2026 · 23-May-26 → 26-May-26

• The Revenge of The Measurers — blunt essay: May 2026 tech layoffs are here (Meta -8,000, Cloudflare first mass layoff in 16 years, 100k+ YTD); the claim “they just overhired during COVID” has been quietly dropped by VCs; argues AI is cutting the organizational middle first — the “measurers” (middle management, finance, legal, internal audit) — because their function was managing complexity that AI now handles; Peter Drucker framing: only producers and marketers create value, everyone else is cost (opinion · #layoffs, #ai-impact, #future-of-work, #white-collar-jobs)
• Amazon Web Services — Four Years and Out — personal account of being fired from AWS after 4 years on the open source strategy team; describes Amazon’s view of employees as “fungible” (replaceable); hired by a manager who called him “non-fungible” (a specialist); that manager was reorganized out; the tension: Amazon’s fulfillment-center HR model doesn’t translate to institutional knowledge roles; also cites GenAI over-focus as a secondary driver of dissatisfaction (opinion · #aws, #open-source, #big-tech, #career, #layoffs)
• Reverse centaurs and the failure of AI — Cory Doctorow: centaurs = human+machine doing more than either alone (chess grandmasters + software); reverse centaurs = machine using human for support, not the other way around; Amazon Mechanical Turk is the archetype; warehouse robots didn’t remove physically punishing tasks, they made workers pace-setters for machines; a 2021 concept that has aged well as a frame for AI-accelerated labor transformation (opinion · #human-ai-collaboration, #automation, #labor, #ai-ethics)
• Coding agents are giving everyone decision fatigue — AI makes code generation cheap but makes human judgment more expensive; work density up, not down; the new scarce resource is the ability to define “what good looks like” (opinion · #ai-coding, #decision-fatigue, #developer-productivity)
• Thoughtworks: Future of Software Engineering Retreat — industry retreat key takeaways; referenced in the olano.dev pieces; covers how code review and quality processes need to change as LLM output exceeds human review capacity (thought-leadership · #software-engineering, #ai-coding, #future-of-work)
• Responsible Work — Satisfice PDF resource on professional responsibility in software work; testing-adjacent; a reference document on what accountable engineering practice looks like (other · #software-quality, #testing, #professional-ethics)

W21 2026 · 16-May-26 → 22-May-26

• Why I Don’t Vibe Code — experienced developer’s personal case against vibe coding: cost friction (token economics feel absurd to a self-described cheapskate), experience-based calm, workflow mismatch; the piece is valuable as a genuine counterpoint from someone with deep experience, not a technophobe
• SharpSkill vs LeetCode — comparison of interview prep tools; SharpSkill targets real-stack mastery (React, Node, Spring, etc.) for non-FAANG interviews; LeetCode targets FAANG algorithm grinders; reflects how AI has shifted interview prep market toward application-layer skills
• I was laid off by Atlassian — personal account (YouTube) of an Atlassian layoff; context in broader tech industry contraction
• Reading code instead of writing code: The underestimated senior discipline — as LLMs generate more code faster, code reading becomes the critical differentiator; senior engineers must audit, understand, and navigate code they didn’t write
• Don’t Outsource the Learning — skill atrophy is subtle: thousands of small copy-paste interactions; engineers who use AI for conceptual questions retain comprehension; copy-pasters don’t

W20 2026 · 09-May-26 → 15-May-26

• Software engineering may no longer be a lifetime career — Goedecke’s structural argument: the learn-by-doing incentive structure is disrupted by AI; not because AI makes you dumber, but because the economic incentive to learn deeply through practice is being dismantled

W19 2026 · 02-May-26 → 08-May-26

• ad-si/Coding-Flashcards — flashcard-based coding practice; noted as potentially useful for interview preparation as a complement to more hands-on tools

Open Questions / Tensions

• Learn-by-doing is broken, now what? Goedecke identifies the structural problem but doesn’t fully resolve it. Harris’s “Why I Don’t Vibe Code” shows that experienced engineers may simply opt out — but that’s not a solution for juniors who need the learning that practice provides.
• Atrophy vs. augmentation: Goedecke and Osmani describe the same phenomenon from different angles — one as economic structure, the other as personal discipline. Both are right. Harris adds a third angle: for some, the economic argument (cost of tokens) is itself the deciding factor.
• Interview prep market shift: SharpSkill vs LeetCode reflects a real fork in the market — are engineers being hired to solve abstract puzzles or to master their actual stack? The answer differs sharply between FAANG and the rest of the industry.
• Layoffs and AI causation: The Atlassian layoff video is data in a broader trend. Hard to attribute individual layoffs to AI directly, but the macro signal — large tech companies shedding engineering headcount — is real and ongoing.