Licensed code footprints, the production modules, the architecture decisions, and shipping B2B SaaS in the AI era — written by the architect.
AI coding tools generate endpoints fast. What they can't shortcut is the design complexity in multi-tenant data isolation, background job idempotency, and file permission layers — these require production-shaped data models designed in advance.
Read →The vibe-coding paradox has a budget expression: AI coding speed gets allocated to features, while platform-layer primitives accumulate debt that bills at enterprise sales time.
Read →Milan Jovanović is running a weekly workflow where agents review production logs and find bugs. The explain step — not the detection — is what matters, and that depends on what module structure the codebase gives the agent to reason against.
Read →ThePrimeagen named the pattern: in the agent era, every change is small, teams never step back, and slop accumulates. The fix isn't a planning ritual — it's structural.
Read →ThePrimeagen's proposal to give agents a state machine constraint surface is the right instinct — but it only works if the codebase already has real module-level states to reason about.
Read →Gergely Orosz made two points this week. The first got all the replies. The second is the one worth working through: making new services easy to spin up has done real damage to software.
Read →When a buyer's technical team opens a homegrown B2B SaaS codebase, they are not checking whether it works. They are checking whether the team that built it knew what they were doing — and whether the next team will be able to maintain it.
Read →ThePrimeagen put the problem clearly this week: in the agent era, there is so much control that is lost. For enterprise B2B SaaS teams, losing control is not a workflow inconvenience — it's an architectural risk.
Read →Karpathy's distinction between vibe coding and agentic engineering is real. The gap between the two isn't skill — it's what the agent has to work with. Code footprints change what agents can do.
Read →The case for staying on .NET Framework isn't technical anymore — it's inertia. The carrying cost of legacy .NET infrastructure is real, ongoing, and growing larger as modern tooling assumes .NET 8.
Read →The conventional advice in 2026 is to start with an ORM and optimize later. The CleenUI codebase has 700+ stored procedures, Dapper, and no ORM. Here is what that decision actually means in production.
Read →Gergely Orosz made the case this week that AI-assisted development makes Big Upfront Planning viable again — reversing a core Agile objection. What shifts for engineers and the founders who fund them.
Read