--- title: The bottleneck isn't writing code anymore. It's... description: As AI agents generate code at unprecedented speed, the real bottleneck has shifted from writing code to understanding and taking accountability for it.... canonical: https://daily.dev/posts/the-bottleneck-isn-t-writing-code-anymore-it-s-understanding-it--oqefvqhf8 twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: The bottleneck isn't writing code anymore. It's understanding it. | daily.dev og:description: As AI agents generate code at unprecedented speed, the real bottleneck has shifted from writing code to understanding and taking accountability for it.... og:url: https://daily.dev/posts/the-bottleneck-isn-t-writing-code-anymore-it-s-understanding-it--oqefvqhf8 og:image: https://api.daily.dev/og/posts/OqEfvQhF8.png og:image:alt: The bottleneck isn't writing code anymore. It's understanding it. og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # The bottleneck isn't writing code anymore. It's understanding it. **[Three Dots Labs](https://daily.dev/sources/threedotslabs)** · 8 min read · 152 upvotes · 31 comments ## Summary As AI agents generate code at unprecedented speed, the real bottleneck has shifted from writing code to understanding and taking accountability for it. Reviewing AI-generated code is harder than reviewing human-written code because context must be rebuilt from scratch, making readability and good coding practices more important than ever. The author argues that established principles like DDD and Clean Architecture remain relevant — not for machines, but for the humans who must own what they ship. Not all software is equal: vibe-coded prototypes differ fundamentally from production-grade systems, and teams that skip code review risk outages and long-term slowdowns. The key insight is that generating code fast means nothing if you can't verify it works, doesn't break things, and solves the right problem. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Community discussion Top comments from developers on daily.dev. **@confidentcoding** · 18 upvotes > Actually, not really. The bottleneck is exactly the same. If you don't write code, you don't understand it, and that is the cold hard truth. > > Articles like this only speak to one single demographic (those that have had years or decades of pre-AI coding experience) just dance around [the paradox](https://daily.dev/posts/ai-coding-will-prevent-expertise-the-need-for-ongoing-friction-in-long-term-skill-formation--qiv3i2hlk): > > If these tools _demand expertise_, yet the tools can _actively circumvent_ the friction that _cultivates expertise_, then what is the path for one to _become an expert_ so... **@musikk** · 3 upvotes > I think this is all a bit shortsighted. I believe our current way of composing and reviewing code as individual lines of code has to evolve to a higher level of abstraction. As the author says, they don't review the frontend as long as it looks good. By the same reasoning you can easily invert it and say you don't care about the backend, it's only some stupid CRUD with a little bit of logic sprinkled in there. Of course it depends on the nature of the application you're working on. But fundamentally I believe we should work towards something where you don't have to fully read either but still... **@ra\_jeeves** · 3 upvotes > The bottleneck isn't understanding the code, it is the "desire" to understand it. > > > If you truly want to understand it, you'll try and in the end hopefully get it. But, if the desire itself is missing, then no one can help you. **@lorinreyes** · 3 upvotes > Exactly. > > I totally agree with you. > > Nowadays the bottleneck isn't writing code anymore, it is reviewing and revising. > > I have a personal experience of having to rewrite the whole code after trying to fix a tiny but fatal bug from the giant code base that was generated in less than a week. > > I think reading the whole codebase is not realistic when it is huge, and blind fixing with AI is changing the bad to worse. > > So I personally think that while writing code is no more bottleneck, defining problems and development stages as AI-friendly is the most important part of the project. **@roguealien** · 1 upvotes > and how do we solve it? That's right by learning how to write code... 🤦🏼‍♂️ ## Similar posts on daily.dev - [Code review isn't your bottleneck, even with AI](https://daily.dev/posts/code-review-isn-t-your-bottleneck-even-with-ai-towvrsjdn) · OctopusDeploy · 3 upvotes · 1 comments - [The Final Bottleneck](https://daily.dev/posts/the-final-bottleneck-ceqadcl8q) · Armin Ronacher · 2 upvotes · 2 comments --- Tags: [#architecture](https://daily.dev/tags/architecture), [#ai-coding](https://daily.dev/tags/ai-coding), [#code-review](https://daily.dev/tags/code-review), [#domain-driven-design](https://daily.dev/tags/domain-driven-design) [View this post on daily.dev](https://daily.dev/posts/the-bottleneck-isn-t-writing-code-anymore-it-s-understanding-it--oqefvqhf8) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"The bottleneck isn't writing code anymore. It's understanding it.","url":"https://daily.dev/posts/the-bottleneck-isn-t-writing-code-anymore-it-s-understanding-it--oqefvqhf8","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/the-bottleneck-isn-t-writing-code-anymore-it-s-understanding-it--oqefvqhf8"},"datePublished":"2026-08-06T12:14:55.639Z","dateModified":"2026-08-06T12:15:17.113Z","description":"As AI agents generate code at unprecedented speed, the real bottleneck has shifted from writing code to understanding and taking accountability for it....","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/bfcd66fe6c83147f9774c940955e85aa?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/bfcd66fe6c83147f9774c940955e85aa?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Three Dots Labs","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Three Dots Labs","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/8060f0b72e3f4f008b8b6f313627c2f2","url":"https://daily.dev/sources/threedotslabs"},"commentCount":31,"discussionUrl":"https://daily.dev/posts/the-bottleneck-isn-t-writing-code-anymore-it-s-understanding-it--oqefvqhf8","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":152},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":31}],"keywords":"architecture,ai-coding,code-review,domain-driven-design","timeRequired":"PT8M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Three Dots Labs","item":"https://daily.dev/sources/threedotslabs"},{"@type":"ListItem","position":3,"name":"The bottleneck isn't writing code anymore. It's understanding it."}]} {"@context":"https://schema.org","@type":"WebPage","@id":"https://daily.dev/posts/the-bottleneck-isn-t-writing-code-anymore-it-s-understanding-it--oqefvqhf8","comment":[{"@type":"Comment","text":"Actually, not really. The bottleneck is exactly the same. If you don’t write code, you don’t understand it, and that is the cold hard truth.\nArticles like this only speak to one single demographic (those that have had years or decades of pre-AI coding experience) just dance around the paradox:\nIf these tools demand expertise, yet the tools can actively circumvent the friction that cultivates expertise, then what is the path for one to become an expert so they can effectively use these tools?","datePublished":"2026-08-06T13:48:47.814Z","dateModified":"2026-08-06T13:49:09.406Z","url":"https://daily.dev/posts/OqEfvQhF8#c-ocfp563pi","author":{"@type":"Person","name":"Lars Faye | Confident Coding","url":"https://daily.dev/confidentcoding","image":"https://media.daily.dev/image/upload/s--OGZu5DEc--/f_auto/v1772569630/avatars/avatar_umWZ9aQAng34qk5aaJl2q?_a=BAMAMiiu0"},"interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":18}},{"@type":"Comment","text":"I think this is all a bit shortsighted. I believe our current way of composing and reviewing code as individual lines of code has to evolve to a higher level of abstraction. As the author says, they don’t review the frontend as long as it looks good. By the same reasoning you can easily invert it and say you don’t care about the backend, it’s only some stupid CRUD with a little bit of logic sprinkled in there. Of course it depends on the nature of the application you’re working on. But fundamentally I believe we should work towards something where you don’t have to fully read either but still be able to understand how it’s put together. I have no idea how that could look like though.\nThat being said, it’s already possible to improve the review process with AI. I know, many people think AI looking at AI code is bad but if you think about it, that’s like saying “code review doesn’t work if humans read human written code”. Writing and reading/reviewing are two entirely different contexts and it’s difficult to be in both at the same time. How many times did you write something only for a very obvious problem being pointed out in a review? Rushing forward and pushing back in a cycle until you end up in a good spot. I’m working with AI reviewers every day and the amount of mistakes in tricky state transitions or data propagations they catch is astonishing. Many of those edge cases would never have been caught by a human and live on as bugs in edge case scenarios. It allows me as a reviewer to relax a little and look more at the bigger picture. I don’t follow all the plumbing and gloss over it. Instead I concentrate on which systems talk to which other systems and how they exchange data. Not how each and every single datapoint is passed along. And this is the light version of a higher abstraction. We just need a more formal notation for this that allows us to hide those details unless we explicitly want to look into them.","datePublished":"2026-08-07T07:50:40.835Z","url":"https://daily.dev/posts/OqEfvQhF8#c-23aHrwzlo","author":{"@type":"Person","name":"Werner Hahn","url":"https://daily.dev/musikk","image":"https://lh3.googleusercontent.com/a/ACg8ocJr9LIXrt1E5zAmLx3QtOkq4iGvcwdh-t__bh6z4dhVoZyOEgE=s96-c"},"interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":3}},{"@type":"Comment","text":"The bottleneck isn’t understanding the code, it is the “desire” to understand it.\nIf you truly want to understand it, you’ll try and in the end hopefully get it. But, if the desire itself is missing, then no one can help you.","datePublished":"2026-08-09T06:45:25.126Z","url":"https://daily.dev/posts/OqEfvQhF8#c-GXg1f7nUm","author":{"@type":"Person","name":"Rajeev R. Sharma","url":"https://daily.dev/ra_jeeves","image":"https://media.daily.dev/image/upload/s--GSwfHept--/f_auto/v1753591600/avatars/avatar_vCVYeh9h4cCzsBSvu21b0?_a=BAMClqZW0"},"interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":3}},{"@type":"Comment","text":"Exactly.\nI totally agree with you.\nNowadays the bottleneck isn’t writing code anymore, it is reviewing and revising.\nI have a personal experience of having to rewrite the whole code after trying to fix a tiny but fatal bug from the giant code base that was generated in less than a week.\nI think reading the whole codebase is not realistic when it is huge, and blind fixing with AI is changing the bad to worse.\nSo I personally think that while writing code is no more bottleneck, defining problems and development stages as AI-friendly is the most important part of the project.","datePublished":"2026-08-07T02:05:47.698Z","url":"https://daily.dev/posts/OqEfvQhF8#c-JUNwoSnPH","author":{"@type":"Person","name":"Lorin Reyes","url":"https://daily.dev/lorinreyes","image":"https://media.daily.dev/image/upload/s--iUqTXLqI--/f_auto/v1785636774/avatars/avatar_sjwvePDvHVHLi0ZolZR6k?_a=BAMAMicg0"},"interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":3}},{"@type":"Comment","text":"and how do we solve it? That’s right by learning how to write code… 🤦🏼‍♂️","datePublished":"2026-08-15T13:56:29.952Z","url":"https://daily.dev/posts/OqEfvQhF8#c-xOWNSegFY","author":{"@type":"Person","name":"Rodrigo García","url":"https://daily.dev/roguealien","image":"https://avatars0.githubusercontent.com/u/6985253?v=4"},"interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":1}}]} ```