A blog post from developer Mastro Js argues that agentic AI coding tools risk repeating a 'deskilling' cycle that already reshaped frontend engineering over the past decade — and that the industry should pay attention before it happens again.
Writing on his blog on May 23, 2026, Mastro Js argues that deskilling occurs when specialized labor is replaced by technologies operable by semi-skilled workers. He points to the earlier rise of heavy JavaScript frameworks and pre-built UI components, which he says let generalist developers bypass core browser mechanics like semantic HTML, accessibility, and network performance — lowering both the skill floor and, over time, developer bargaining power.
His argument is that agentic AI extends this same pattern across general software engineering. Unlike traditional compilers, which translate high-level code deterministically, he describes large language models as behaving like high-dimensional search engines that fill in omitted details based on context and training data — an approach that leads to edge-case failures when those abstractions leak.
Mastro Js draws several parallels between past tooling shifts and the current agentic AI wave:
- Reduced barriers vs. bargaining power: lowering the skill floor makes it easier for businesses to swap developers across projects, which he argues reduces worker leverage and compensation.
- Leaky abstraction failure: AI-generated code can omit architectural nuance, so experienced engineers are still needed to diagnose runtime failures when generated code breaks.
- Disconnection from quality: he contends commercial success rarely correlates directly with software quality, which pushes companies toward shipping speed over maintainability.
- A 'Bauhaus' alternative: rather than rejecting automation or accepting degraded output, he argues developers should integrate AI tooling with deep engineering craft rather than let it substitute for it.
He acknowledges limits to his own argument: LLMs speed up boilerplate work but lack deterministic reasoning, and configuration files such as AGENTS.md or SKILL.md don't replace a developer's need to manually inspect and verify generated code within a larger codebase.
The piece is an opinion argument, not a report grounded in industry data or surveys, so its claims about deskilling trends and worker bargaining power should be read as one developer's interpretation rather than an established industry finding.