Close Menu
    DevStackTipsDevStackTips
    • Home
    • News & Updates
      1. Tech & Work
      2. View All

      CodeSOD: A Unique Way to Primary Key

      July 22, 2025

      BrowserStack launches Figma plugin for detecting accessibility issues in design phase

      July 22, 2025

      Parasoft brings agentic AI to service virtualization in latest release

      July 22, 2025

      Node.js vs. Python for Backend: 7 Reasons C-Level Leaders Choose Node.js Talent

      July 21, 2025

      The best CRM software with email marketing in 2025: Expert tested and reviewed

      July 22, 2025

      This multi-port car charger can power 4 gadgets at once – and it’s surprisingly cheap

      July 22, 2025

      I’m a wearables editor and here are the 7 Pixel Watch 4 rumors I’m most curious about

      July 22, 2025

      8 ways I quickly leveled up my Linux skills – and you can too

      July 22, 2025
    • Development
      1. Algorithms & Data Structures
      2. Artificial Intelligence
      3. Back-End Development
      4. Databases
      5. Front-End Development
      6. Libraries & Frameworks
      7. Machine Learning
      8. Security
      9. Software Engineering
      10. Tools & IDEs
      11. Web Design
      12. Web Development
      13. Web Security
      14. Programming Languages
        • PHP
        • JavaScript
      Featured

      The Intersection of Agile and Accessibility – A Series on Designing for Everyone

      July 22, 2025
      Recent

      The Intersection of Agile and Accessibility – A Series on Designing for Everyone

      July 22, 2025

      Zero Trust & Cybersecurity Mesh: Your Org’s Survival Guide

      July 22, 2025

      Execute Ping Commands and Get Back Structured Data in PHP

      July 22, 2025
    • Operating Systems
      1. Windows
      2. Linux
      3. macOS
      Featured

      A Tomb Raider composer has been jailed — His legacy overshadowed by $75k+ in loan fraud

      July 22, 2025
      Recent

      A Tomb Raider composer has been jailed — His legacy overshadowed by $75k+ in loan fraud

      July 22, 2025

      “I don’t think I changed his mind” — NVIDIA CEO comments on H20 AI GPU sales resuming in China following a meeting with President Trump

      July 22, 2025

      Galaxy Z Fold 7 review: Six years later — Samsung finally cracks the foldable code

      July 22, 2025
    • Learning Resources
      • Books
      • Cheatsheets
      • Tutorials & Guides
    Home»Tech & Work»The emperors of AI coding tools have no clothes – and it’s creating a productivity delusion

    The emperors of AI coding tools have no clothes – and it’s creating a productivity delusion

    May 20, 2025

    For three years, I’ve watched the AI coding revolution unfold with a mix of fascination and frustration. As someone who’s built and led AI engineering and product teams at Google, SwiftKey, Yahoo, and beyond, I’m calling it: we’re collectively falling for a productivity mirage. 

    We’re celebrating typing speed while ignoring the actual bottlenecks that cripple software development and most annoy dev teams. 

    Developers only spend a couple of hours daily writing code, and they hate this. They spend most of their time “not making their beer taste better”, and doing soul-sucking boring work. Scaffolding projects, managing tickets, refining stories, fixing bugs, handling tech debt, writing tests, fixing build issues… you only need to look at the Stack Overflow blog to hear the outcry. Yet, as a society, we’re pouring millions into making those 1-2 hours marginally faster – those hours where devs actually have the most fun.

     The problem with dopamine

    We are witnessing what I call “the 80% problem” across the industry – a dopamine hit that hides the real pain. What do I mean by this? I used to joke that, with bad management, “the first 80% takes 20% of the time, and the remaining 20% takes… 80% of the time”. Well, we’re managing AI badly. Current AI tools get you 80% of the way quickly, creating a dopamine hit of productivity. It is the last 20% that wastes all your time savings. It’s like sprinting the first 19 miles of a marathon and feeling great, but then having absolutely no legs to finish off the remaining 7 miles you have left.

    It’s that 20% that contains most of the subtle bugs because AI has made a litany of minute errors that have piled up, without oversight. It’s  this final 20% that represents the actual design challenge requiring human expertise – and honestly, that should have been done in collaboration with the AI, not after the AI. The result is a psychological mirage where developers feel productive initially, but team velocity remains stubbornly unchanged. Even worse, you’re building up technical debt in the form of poor quality that, over time, means your product and technology starts to slowly crumble under the AI code-slop.

    This tunnel vision is baffling if you’re a competent manager. To draw on another analogy – imagine Toyota revolutionizing manufacturing by only optimizing how quickly workers insert screws, while ignoring the entire production line. We’d laugh at such limited thinking. Yet this is precisely what’s happening with AI coding tools.

    A recent Wired survey of 730 developers captured this perfectly, with many seeing AI as “useful, but clueless”—essentially a hyperefficient intern that still can’t handle context, edge cases, or real problem-solving. This matches exactly what I’ve observed in enterprise environments.

    Speaking with CTOs across the industry, I’ve yet to find one who can demonstrate consistent, measurable improvement in delivery metrics from their AI investments. Where are the SEC filings showing reliable 20+% speedups? They don’t exist, because we’re optimizing the wrong things.

    Instead, we’re transforming developers into glorified secretaries for AI – manually ferrying context between systems, copy-pasting specifications, and cleaning up hallucinated code. The bitter irony is that tools meant to eliminate tedious work have created a new form of drudgery, removed the fun, and even created new messes. You’re not using the AI—you’re serving it. It’s easy to feel productive initially, but it’s not sustainable unless you bring complete context to the AI… at which point you’re essentially working for the AI, not the other way around.

    Suffering from buyer’s remorse?

    Given the frenzy of spending over the past few years, I can’t just complain, so here’s some remedial advice to those CTOs who didn’t keep the receipt on those AI coding tools:

    First, demand measurement beyond vanity metrics. Focus exclusively on time from a well-written ticket to deployment – that’s the only throughput that matters. Don’t ask devs whether they “feel more productive” because they have outsourced thinking to AIs.

    Second, prioritize quality alongside speed. You can’t accept that writing subtle defects into your code faster is a good trade-off. Context is everything in engineering, and tools that can’t access and understand your full development context will always deliver subpar results. Tools should discover the context for you; why are you chasing down context for the AI? Are the tools looking at tests and architecture docs automatically? Are they running what they write against your tests automatically and fixing the issues? Are they running your linters or following your most basic coding requirements?

    Third, widen your scope of optimization, don’t narrow it. This feels counterintuitive – we’re taught to ship in thin slices. But the greatest system improvements come from global optimizations, not local ones. It’s like my experience building IoT devices: rather than squeezing 15% better performance by optimizing a power-hungry GPS chip, we solved the local problem by solving it globally: we added a 2-cent motion sensor and a 5-cent low-power processor that triggered the GPS only when needed, transforming battery life entirely.

    The truly transformative opportunity lies in removing entire steps from your process, not optimizing individual ones. Why are we paying senior engineers £150k to manually create branches and scaffold boilerplate code? Why do we care at all about typing speed now? 

    Consider Stripe and Netflix – their competitive advantage comes not from typing code faster but from ruthlessly eliminating handoffs and bottlenecks between teams. Stripe invested heavily in streamlining code reviews, testing automation, and deployments between engineering, product, QA, and operations teams. Netflix focused on automated delivery pipelines and chaos engineering practices that minimized bottlenecks between dev, ops, and deployment teams, enabling rapid global deployments.

    This isn’t just about efficiency – it’s a strategic advantage. While others celebrate marginal coding gains, companies addressing the full development lifecycle are entering markets faster and responding to customer needs before competitors even understand the requirements. It’s the difference between market leadership and irrelevance. And you have a bit of time before your competitors wake up and move on this before you do – but time is quickly running out.

    The path forward is clear: treat AI as a system that completes entire tasks, not as a glorified autocomplete. Measure success through meaningful DORA metrics, not lines of code generated. And demand that AI adapts to your team’s established processes, not vice versa.

    The question isn’t whether AI will transform software development. It absolutely will. The question is whether we’ll optimize what actually matters. And whether you’re leading or following.

    The post The emperors of AI coding tools have no clothes – and it’s creating a productivity delusion appeared first on SD Times.

    Source: Read More 

    news
    Facebook Twitter Reddit Email Copy Link
    Previous ArticleGoogle I/O: Updates across Gemini, Android Studio, Google Play, and more
    Next Article HCL Commerce V9.1 – The Power of HCL Commerce Search

    Related Posts

    Tech & Work

    CodeSOD: A Unique Way to Primary Key

    July 22, 2025
    Tech & Work

    BrowserStack launches Figma plugin for detecting accessibility issues in design phase

    July 22, 2025
    Leave A Reply Cancel Reply

    For security, use of Google's reCAPTCHA service is required which is subject to the Google Privacy Policy and Terms of Use.

    Continue Reading

    CVE-2025-5407 – “Chaitak-Gorai Blogbook Cross-Site Scripting Vulnerability”

    Common Vulnerabilities and Exposures (CVEs)

    Laracon US tickets are on sale

    Development

    How to Get Information About Your Linux System Through the Command Line

    Development

    CVE-2025-46828 – WeGIA Web Manager SQL Injection Vulnerability

    Common Vulnerabilities and Exposures (CVEs)

    Highlights

    News & Updates

    Is Microsoft’s new AI still “4x more accurate than human doctors”? — Typos in medical prompts to chatbots could be catastrophic

    July 10, 2025

    A new study highlights how a simple typo can prompt an AI-powered tool to incorrectly…

    CVE-2025-46840 – Adobe Experience Manager Privilege Escalation Improper Authorization

    June 10, 2025

    CVE-2025-34048 – D-Link ADSL Router Path Traversal Vulnerability

    June 26, 2025

    ThumbnailPilot

    May 11, 2025
    © DevStackTips 2025. All rights reserved.
    • Contact
    • Privacy Policy

    Type above and press Enter to search. Press Esc to cancel.