惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

GbyAI
GbyAI
Martin Fowler
Martin Fowler
云风的 BLOG
云风的 BLOG
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
T
The Blog of Author Tim Ferriss
大猫的无限游戏
大猫的无限游戏
A
About on SuperTechFans
小众软件
小众软件
博客园_首页
博客园 - 聂微东
罗磊的独立博客
Recent Announcements
Recent Announcements
U
Unit 42
N
Netflix TechBlog - Medium
Blog — PlanetScale
Blog — PlanetScale
阮一峰的网络日志
阮一峰的网络日志
博客园 - 叶小钗
V
V2EX
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
IT之家
IT之家
Stack Overflow Blog
Stack Overflow Blog
博客园 - Franky
D
DataBreaches.Net
Last Week in AI
Last Week in AI

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
Experienced devs are 19% slower with AI tools. They just ...
Aditya Agarwal · 2026-05-24 · via DEV Community

Senior developers are 19% slower when using AI coding tools. But they think they're faster. That gap should terrify you.

A recent study measured experienced developers using AI-assisted coding tools on real tasks. The result? A measurable 19% slowdown compared to working without AI. The kicker is what happened next.

Those same developers reported feeling more productive. But no, it didn't. Not really. Not even close.

The vibes-over-metrics problem

This is the part that I find concerning and affects my sleep. We're making tooling decisions based on how things feel, not what actually happens.

I understand the temptation, though. It's so tangible. After Copilot writes 40 lines of code for you, hitting Tab feels so satisfying. It almost feels like you just saved five minutes. But did you? Or did you spend the next ten minutes reading, verifying, tweaking, and debugging ten lines of code that you didn't technically write?

The sensation of speed is not speed. And we're confusing the two across the entire industry.

Why senior devs get hit hardest

It does sound counterintuitive, right? Shouldn't experienced developers be better at using AI tools? They know what good code looks like. They can identify and reject poor recommendations more quickly.

My hypothesis is that this is the crux of the issue. Senior devs have opinions, strong opinions about quality, about architecture, about names. And so when the AI suggests something almost right, they don't just accept it. They enter an edit loop and restructure and tweak and refactor the suggestion until it meets their bar. A junior dev might just hit Tab and get on with it.

→ The AI generates plausible code fast.
→ The senior dev knows "plausible" isn't good enough.
→ The review-and-fix cycle eats the time the AI supposedly saved.
→ But the feeling of "the AI wrote most of it" persists.

Hiring an AI to do your work is like hiring a fast, sloppy intern. You may think you're delegating tasks, but you're actually just spending time fixing the mistakes they made. 😅

The false confidence crisis

This is not merely a specific personal productivity issue. It is developing into a blind spot for the entire industry.

Teams are adopting AI tools and assuming productivity gains without measuring them. They notice that their developers are starting to use Copilot and they automatically mark the "AI-enabled" checkbox. No one stops to compare the results. No one monitors whether the sprint velocity has actually increased.

We are developing a strategy based on intuition.

And when someone raises a hand and says "I'm not sure this is actually helping," the response is predictable: "You're just not using it right." That's not engineering. It's a matter of faith.

What I actually think we should do

I'm not anti-AI tooling. I use it daily. But I think we need to be brutally honest about where it helps and where it doesn't.

Measure, don't assume. If your team adopted AI tools, compare actual output before and after. Not feelings. Output.
Recognize the edit tax. Every AI suggestion you modify still costs cognitive load. That cost is invisible but real.
Stop treating skepticism as resistance. Developers questioning AI productivity aren't Luddites. They might be the only ones paying attention to the data.

The research that uncovered these results had more than 800 comments on a developer community thread. The volume alone indicates that this struck a chord because developers already had a feeling that something was off but now they have the data to back it up. 🔥

The uncomfortable takeaway

The most dangerous outcome isn't that AI tools are slow. Tools improve. Models get better. Context windows grow.

The problem is that we are not aware when we are actually slower. If how we feel about what we are doing is disconnected from what is actually happening, then we are no longer in a good position to make sensible decisions about what we work on. That’s a trust-in-yourself issue, not a tooling issue.

So here's my question: Have you ever actually measured whether AI tools make you faster — with real data, not gut feeling? I'd genuinely love to hear what you found. I am really interested to know.