--- title: Are you walking your AI, or is your AI walking you? description: Delegating software architecture to LLMs is a critical mistake that violates foundational software engineering principles. Drawing on Fred Brooks' conceptual... canonical: https://daily.dev/posts/are-you-walking-your-ai-or-is-your-ai-walking-you--3zmw1ohee twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Are you walking your AI, or is your AI walking you? | daily.dev og:description: Delegating software architecture to LLMs is a critical mistake that violates foundational software engineering principles. Drawing on Fred Brooks' conceptual... og:url: https://daily.dev/posts/are-you-walking-your-ai-or-is-your-ai-walking-you--3zmw1ohee og:image: https://api.daily.dev/og/posts/3zMW1OhEE.png og:image:alt: Are you walking your AI, or is your AI walking you? 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. # Are you walking your AI, or is your AI walking you? **[Bilal A](https://daily.dev/sources/fyqjozd88mvcashhqdzxg)** · [@bilala8](https://daily.dev/bilala8) · 5 min read · 1 upvotes · 0 comments ## Summary Delegating software architecture to LLMs is a critical mistake that violates foundational software engineering principles. Drawing on Fred Brooks' conceptual integrity, Rich Hickey's simplicity philosophy, and warnings from Joe Armstrong and Niklaus Wirth, the argument is that LLMs produce averaged, complected architectures lacking unified vision. More dangerously, outsourcing design prevents developers from building the mental model needed to debug and maintain systems under pressure. AI should handle tactical code generation while humans retain full ownership of system design. ## Content **TL;DR:** AI is a phenomenal typist but a terrible Chief Architect. Delegating system design to LLMs violates decades of established software engineering principles from giants like Brooks, Hickey, and Wirth. AI defaults to complexity, lacks a unified vision, and prevents you from building the mental model you'll desperately need when production goes down at 3:00 AM. Reclaim the whiteboard. ## The LLM Architect is a Lie: Why Delegating System Design Will Destroy Your Codebase We are living in the golden age of code generation. Need a React component? Prompt it. Need a boilerplate CRUD endpoint? Tab-complete it. As a vibe coder since GPT3, I can tell you firsthand: Large Language Models are fantastic at these tactical, localized tasks. But a dangerous trend is quietly taking root in the engineering community. Seduced by the speed of AI, developers are starting to delegate not just the code, but the _architecture_. They are asking LLMs to design distributed systems, define microservice boundaries, and establish data models. This is a catastrophic mistake. Software engineering has never been about typing speed; it is fundamentally about managing complexity within the limits of the human brain. When you outsource system design to an LLM, you aren't just cutting corners—you are violating the core principles of software engineering established by the industry’s greatest minds. Here is why your "AI Architect" is building a house of cards, and why you must reclaim the whiteboard. ### 1. The Death of "Conceptual Integrity" (Fred Brooks) In _The Mythical Man-Month_, Fred Brooks laid down a law that has survived decades of paradigm shifts. He didn't just suggest having a unified vision; he demanded it: > _"Conceptual integrity in turn dictates that the design must proceed from one mind, or from a very small number of agreeing resonant minds."_ An LLM is the exact opposite of "one mind." It is a probabilistic engine trained on the amalgamation of millions of different developers, varying architectures, and conflicting paradigms across GitHub and Stack Overflow. When you ask an AI to design a system, it doesn't give you a unified vision. It gives you an average of the internet. It will happily mix domain-driven design with anemic data models, or tightly couple services while calling them "micro." Without a human Chief Architect enforcing conceptual integrity, your system becomes a stitched-together Frankenstein of statistical guesses. ### 2. The AI Default is "Complected" (Rich Hickey) In his seminal talk _Simple Made Easy_, Clojure creator Rich Hickey fundamentally changed how we view complexity by breaking down the etymology of the words themselves: > _"Simplicity is objective. It means 'one fold' or 'one braid.'... Complecting is interleaving... braiding things together."_ LLMs do not naturally build "one-fold" systems. Because they predict the next most likely token based on vast amounts of enterprise code, their default state is to generate standard, boilerplate-heavy, heavily abstracted architectures. They complect (intertwine) state, logic, and infrastructure because that is what the bulk of their training data looks like. True architectural simplicity requires tearing down complexity until only the essential remains. AI adds; it rarely subtracts. ### 3. You Can't Maintain What You Can't Grasp (Armstrong & Wirth) Erlang creator Joe Armstrong often lamented the loss of **Total Understanding**. He pointed out that early programs were constrained by hardware (fitting into 64KB or 128KB of memory), which forced them to be small enough to fit entirely inside a single programmer's head. Similarly, Turing Award winner Niklaus Wirth warned us in _A Plea for Lean Software_ about the dangers of unchecked scale: > _"Increasingly, people seem to misinterpret complexity as sophistication."_ This is the most dangerous trap of the LLM architect. When you design a system yourself, you build a mental model of it. You know where the data flows, you know where the bottlenecks are, and you know _why_ certain tradeoffs were made. When you prompt an AI to generate an architecture for you, you bypass the cognitive struggle required to build that mental model. You might have a repository full of code, but you possess zero _Total Understanding_. When the production database is deadlocking at 3:00 AM and customers are screaming, the LLM cannot take the pager. You have to debug a system you did not conceptualize, and because you didn't design it, you won't be able to fix it. ### The Verdict: Retain the Whiteboard AI is a powerful typist. It is a tireless pair programmer. It is a phenomenal tool for bridging the gap between an idea in your head and syntax in your editor. But the architecture—the _idea_ itself—must remain yours. Protect the conceptual integrity of your systems. Fight for simplicity. Keep the system small enough to fit inside your brain, because an LLM doesn't have a brain to store it in. Use AI to write the functions, but if you want your codebase to survive, you must remain the architect. ## Similar posts on daily.dev - [Stop generating, start thinking](https://daily.dev/posts/stop-generating-start-thinking-7jjvm8uwh) · Hacker News · 16 upvotes · 1 comments - [Butlers or Architects?](https://daily.dev/posts/butlers-or-architects--lxinmf2dl) · Metadata · 2 upvotes · 0 comments - [Stop Being an AI Babysitter: How to Use LLMs Without Losing Code Ownership](https://daily.dev/posts/stop-being-an-ai-babysitter-how-to-use-llms-without-losing-code-ownership-1cbod061k) · Sergio Lema · 31 upvotes · 4 comments --- Tags: [#career](https://daily.dev/tags/career), [#architecture](https://daily.dev/tags/architecture), [#llm](https://daily.dev/tags/llm), [#ai-assisted-development](https://daily.dev/tags/ai-assisted-development) [View this post on daily.dev](https://daily.dev/posts/are-you-walking-your-ai-or-is-your-ai-walking-you--3zmw1ohee) ```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":"DiscussionForumPosting","mainEntityOfPage":"https://daily.dev/posts/are-you-walking-your-ai-or-is-your-ai-walking-you--3zmw1ohee","headline":"Are you walking your AI, or is your AI walking you?","text":"Delegating software architecture to LLMs is a critical mistake that violates foundational software engineering principles. Drawing on Fred Brooks' conceptual integrity, Rich Hickey's simplicity philosophy, and warnings from Joe Armstrong and Niklaus Wirth, the argument is that LLMs produce averaged, complected architectures lacking unified vision. More dangerously, outsourcing design prevents developers from building the mental model needed to debug and maintain systems under pressure. AI should handle tactical code generation while humans retain full ownership of system design.","url":"https://daily.dev/posts/are-you-walking-your-ai-or-is-your-ai-walking-you--3zmw1ohee","datePublished":"2026-03-25T23:15:23.799Z","dateModified":"2026-03-25T23:17:37.935Z","author":{"@type":"Person","name":"Bilal A","url":"https://daily.dev/bilala8","image":"https://lh3.googleusercontent.com/a/ACg8ocJ5TzBt7kMU6AdOw71JjE2o8IFIQICdSy-AsvLyj092SEVdzw=s96-c","interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"EndorseAction"},"userInteractionCount":60}},"image":"https://media.daily.dev/image/upload/s--qE4fSHXp--/f_auto/v1774480524/posts/3zMW1OhEE?_a=BAMAMiWQ0","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":1},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"isPartOf":{"@type":"WebPage","url":"https://daily.dev/sources/fyqjozd88mvcashhqdzxg","name":"Bilal A"}} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Bilal A","item":"https://daily.dev/sources/fyqjozd88mvcashhqdzxg"},{"@type":"ListItem","position":3,"name":"Are you walking your AI, or is your AI walking you?"}]} ```