The Reality of AI Coding

Atul Jalan

Atul Jalan

Follow

4 min read

May 27, 2025

There is something that's been bugging me recently about all the online discourse surrounding AI coding: as time goes on, it feels like less and less of it applies to me.

Let me offer an example:

The newest industry craze seems to be commanding a bunch of parallel AI coding agents. We now have Jules, Codex, Devin, Copilot, and soon Cursor offering the ability to spin up dozens of super-intelligent autonomous agents across your codebase to complete the work of 10 engineers in 1/10th of the time (their words, not mine).

Yet, here I am, struggling to get half-way decent results when I ask Cursor to edit more than a single file at once. I can only imagine the colossal waste of time it would be to unleash 50 cursor agents at once across my entire codebase. I am not alone in this.
Online hype is inevitable. You're probably thinking: dude, just get off social media! Go touch some grass (I probably should ...). And to your point, my offline conversations about AI with friends are always much more down to earth. Probably because they all work at large companies on codebases that span millions of lines. Like me, they have more measured takes on AI: super useful, sometimes.

Large codebases is the key, I think. For weekend projects where I couldn't care less about long-term maintainability, I really can make great progress simply by prompting to a working solution. I usually don't even look at the code. But, for my day job, I've converged on a clear set of task-types where I leverage AI, and pretty much avoid it for the rest. It's just not worth the cortisol spike to spend 5 minutes crafting a detailed prompt and attaching all the right context, only to get back a useless result 90% of the time. The gap in AI capabilities between green-field work and mature codebases is astounding.

To be clear, I would actually consider myself a pretty strong AI optimist. It is excellent for greenfield work, for creating a dozen similar API endpoints in minutes, for writing docstrings, for going back-and-forth on tech specs, and for lots of other things too. I think any developer not using AI today is missing out big time. Most importantly, I believe that AI models will continue to improve substantially from where they are today.

But, to date, I have not met a single developer working on a mature codebase who has not had to coddle and meticulously review AI output for anything beyond mostly trivial or greenfield tasks (and I've talked to quite a few!). Many tell me that the time spent prompting and reviewing combined with the high risk of failure and/or subtle bugs has made the cost-benefit calculation top-of-mind when they consider using AI for their work.

A Stanford study found that AI-assisted programmers were more than twice as likely to produce code with security vulnerabilities than their non-AI counterparts. The study was based on having participants complete a series of small, self-contained tasks such as encryption problems, SQL queries, etc. What will happen within real-life codebases when the complexity is orders-of-magnitude higher and the workflow is not AI-assisted but AI-led?

My point with all this is I believe we're headed for some sort of reckoning. With the entire industry hype-cycle going at full tilt, there is huge pressure to adopt AI coding everywhere at breakneck speed, fueled by immense FOMO that has gripped board rooms and c-suites who believe this will moonshot their business.

Shopify recently added AI usage to their performance and peer-review evaluations. No doubt a well-intentioned move to speed AI adoption, but can anyone guess what the second-order effects will be?

I think we are about to start seeing a lot more software that is less secure, less maintainable, less reliable, and less enjoyable to use. Worse, I believe we will see a cultural shift in programming that will deem all this as ok. Outweighed by the productivity gains. This cultural shift will be driven by the same hype-machine that's pushing autonomous superintelligent AI coding agents so hard today.

AI coding com boom
This isn't a call to stop using AI, or stop exploring AI, or stop pushing AI to see how far it can go. Far from it. It's a request to restore some semblance of sanity to the discourse. Because there are real consequences to the way we discuss things.

There will be more Shopifys. One thing I think the crazy AI optimists are correct about: we're still in the early innings. AI coding is here. It is useful. But the reality is not what you see online.

This essay was partially inspired by the following excellent posts:
The Hidden Complexity of Scaling WebSockets

The Hidden Complexity of Scaling WebSockets

WebSockets are at the very core of Compose. Learn how we scaled them to support 1000s of concurrent users.

Smart Debouncer Logic Illustration

Improving UI performance by optimizing our debouncer

Peek into the internals of Compose's UI rendering engine.

Subscibe to our developer newsletter to get occasional emails when we publish new articles and updates.

2025 Compose. All rights reserved.