Ask HN: What is your (AI) dev tech stack / workflow? (June 2026)

TEXT START: "Hello, happy Friday!"

THE DISSECTION

This thread is a speed-read on cognitive automation's invasion of software development, captured in mid-2026. It is not a casual Hacker News thread. It is a live autopsy of a professional class mid-transition. The DT framework maps every response to a precise position on the displacement timeline.

THE CORE FALLACY

The workshop organizer's framing—"upskill through the stages"—presumes AI tools are instruments a skilled human deploys, and that the goal is optimizing human output. This is the fundamental category error of the transition era.

The agent factory operator with ~10k commits/month has already vacated that framework. The limiting resource is no longer human coding ability. It is oversight, architecture design, and process orchestration. The "stages" the organizer imagines (write code → write w/ agent → write w/ multi-agents → orchestrators) are not a staircase the human climbs. They are a conveyor belt the human is being removed from, rung by rung.

The hand-coders and security-company holdouts are not making a lifestyle choice. They are burning lag defenses that will run out.

HIDDEN ASSUMPTIONS

1. "Modern tooling" implies human-in-the-loop as permanent default. It doesn't. The agent factory workflow proves the loop can be opened.

2. AI tools exist to make developers more productive at programming. The agent factory operator is not "more productive at programming." He has largely exited programming. He is running an industrial process.

3. Teaching people to use AI dev tools = employability. The security lead correctly identifies his shop's "strict AI policy" as a lag defense, but wrongfully frames this as a viable long-term strategy. It is hospice care. His "we will fall behind" acknowledgment is the only honest thing in that response.

4. "Vibe coding" is a bad habit one can choose not to adopt. The commenter who warns vibe coders will create messes "they will never recover from" is describing a skill-degradation dynamic, not a moral failing. But this is the wrong target. The mess is irrelevant when the output is cheap enough to be disposable.

5. The workshop can bridge "motivated newbie" to "existing developer using AI." These are not stages of the same journey. The newbie using AI to build apps without learning to code is not a broken version of the developer. She is the first cohort of the post-DT production model. The developer path she bypasses is the one being automated out.

SOCIAL FUNCTION

Transition theater. The thread performs the fiction that software development remains a human profession in active negotiation with AI tools, rather than a profession in active displacement. The distribution of responses maps precisely to DT lag-defense categories:

THE VERDICT

This thread is a document of the crossing, not evidence that the crossing is optional. The person running the agent factory is not an extreme outlier. He is a preview. The 10k-commit/month figure is not impressive relative to what AI-driven development can produce—it is a human bottleneck. The number that matters is not commits per month but architecture decisions per month, and that number is also being automated.

For the workshop organizer specifically: you are designing curriculum for a profession that, per P1 and P2 of the DT framework, will not exist in its current form. "AI harnesses, agents" are not a new tool category to add to the kit. They are the replacement for the kit.

The honest workshop agenda for June 2026: teach people how to own or service the systems that build software. Everything else is teaching people to operate the equipment that will replace them.