---
title: "Your AI Written Backend Works Great… Until You Need to Change Something"
url: https://daily.dev/posts/your-ai-written-backend-works-great-until-you-need-to-change-something-te6v3q7yn
source_url: https://daily.dev/posts/your-ai-written-backend-works-great-until-you-need-to-change-something-te6v3q7yn
type: freeform
source: "WebCraft"
author: "Saad Hasan"
published: 2026-08-24T11:15:37.177Z
updated: 2026-08-24T11:15:50.930Z
tags: ["architecture", "backend", "vibe-coding"]
reading_time: 1
upvotes: 69
comments: 10
language: 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.

# Your AI Written Backend Works Great… Until You Need to Change Something

**[WebCraft](https://daily.dev/sources/webcraft)** · [@saadh393](https://daily.dev/saadh393) · 1 min read · 69 upvotes · 10 comments

## Summary

AI-generated backends tend to become tightly coupled over time, making changes risky once a codebase grows past a few months old. A ports-and-adapters (hexagonal) style architecture pattern is presented through two practical scenarios as a way to keep AI-assisted codebases modular and easier to change, framed without academic theory.

## Content

**AI can build features fast.** But after 6 months, changing one thing can break the whole backend.

That’s the scary part of most AI-generated codebases. Everything becomes tightly connected without you even noticing it.

Recently I was exploring a very interesting architecture pattern that helps solve this problem. I explained it with 2 very real scenarios in a simple way without academic theory.

If you are building products with AI, this architectural thinking is probably more important than ever now.

[🐛 https://saadh393.github.io/blog/adapter-port-architecture-two-cases](https://saadh393.github.io/blog/adapter-port-architecture-two-cases)

## Community discussion

Top comments from developers on daily.dev.

**@apperside** · 4 upvotes

> I think this concept can be expanded generically to every kind of software: people are blindly delegating every aspect of software development to AI, but blindly trusting architecture decision leads to high probable disaster. I think that AI can be blindly trusted only during execution phase of a carefully crafted and reviewed architectural plan. Developing software nowadays is not about writing code anymore, but being able to plan a good architecture and save time by delegating execution to AI

**@pdfopsdev** · 4 upvotes

> hexagonal helps but the real fix is making the boundary itself dumb and typed. ports without a schema at the edge just relocate the coupling, learned that after an AI-generated adapter silently reshaped a field and nothing downstream broke until prod.

**@xynorash** · 2 upvotes

> This is why code reviews are more and more important. Generating code with AI is good but controlling the generated code to be able to handle future changes and still have the "flexible" part is critical for the long run.

**@rsosenke** · 1 upvotes

> Good post. The point that stuck with me: design the port before writing the first adapter. Write the adapter first and the port ends up shaped like that provider’s API, not like what your business logic actually wants to say. Small detail, but it’s the difference between a real port and a wrapper with extra steps.

**@agustinbarrientos** · 0 upvotes

> Architecture tests should reject adapter imports inside business logic. One fixture should prove the rule catches a generated shortcut around the service layer.

## Similar posts on daily.dev

- [A developer’s guide to designing AI-ready frontend architecture](https://daily.dev/posts/a-developer-s-guide-to-designing-ai-ready-frontend-architecture-iv0cryopm) · LogRocket · 6 upvotes · 0 comments

---

Tags: [#architecture](https://daily.dev/tags/architecture), [#backend](https://daily.dev/tags/backend), [#vibe-coding](https://daily.dev/tags/vibe-coding)

[View this post on daily.dev](https://daily.dev/posts/your-ai-written-backend-works-great-until-you-need-to-change-something-te6v3q7yn)