Licensed code footprints, the production modules, the architecture decisions, and shipping B2B SaaS in the AI era — written by the architect.
Gergely Orosz documented that AI coding models fail at Meta and Google because both run monoliths with non-standard tooling. For .NET shops on legacy systems, this is the migration argument updated for 2026.
Read →Scaffolds give you a project structure. Templates give you patterns. Code footprints give you production-validated decisions. In the AI era, the distinction matters: agents can generate into a footprint in ways they cannot generate into a scaffold.
Read →David Fowler is learning a programming language to review AI-generated code, not to write it. If writing is solved, the unsolved problem is knowing what code belongs where — and that's an architecture problem.
Read →Gergely Orosz posted this week about an experienced engineer stopping code review of Fable-generated output — the process felt pointless at that speed. When code review becomes unviable, the quality enforcement layer shifts to the codebase itself.
Read →AI makes it fast to generate a SaaS product. But as Gergely Orosz noted, any company with an actual business eventually owns the maintenance burden of what was generated. The same logic applies before the first line is written.
Read →When AI generates code faster than teams can review it, the old quality gate breaks. The answer isn't a new review process — it's a codebase where structural decisions are already made and enforce themselves.
Read →Greg Isenberg called managing AI agents the most valuable skill of 2026. The framing is close but off by one step. The real skill is knowing what to give agents to generate against — and a production-shaped codebase is the answer.
Read →Milan Jovanović published a video this week on why Robert Martin — 'Uncle Bob' — stopped reading AI-generated code. The readability failure has a structural explanation: code generated without an established pattern to inherit cannot be quickly oriented to. The fix is not a different model.
Read →Addy Osmani published a careful analysis of AI-driven software factories — drawing a clear line between light factories with structural oversight and dark factories without it. The distinction maps directly to an architectural question teams must answer before the first agent session starts.
Read →AI accelerates development at every layer. It also accelerates every architectural mistake. The hard problems in software — multi-tenancy, auth, data modeling, stateful orchestration — don't get simpler with faster generation. They get more expensive when they surface in production.
Read →Dapper + stored procedures was a bet made when CleenUI was designed. In the AI coding era — where generated code hits the data layer constantly — that bet turns out to pay better than expected.
Read →Gergely Orosz observed that standout developers before AI are standout developers with AI. The reason is the fulcrum: the production context they operate on amplifies good engineering judgment. The model is the lever. The codebase is the fulcrum.
Read →Andrej Karpathy drew the line at Sequoia Ascent 2026: vibe coding raises the floor, agentic engineering raises the ceiling. The part that determines which side you're on is the codebase.
Read →A vertical-slice module runs from UI to DB in a complete, coherent cut. When AI generates code against a module that already runs, it has the full context: the component, the endpoint, the service, the stored procedure, the table. That context is what makes generated code integrate.
Read →Dex Horthy laid out the context engineering framework with The Pragmatic Engineer: context quality determines agent output quality. The discussion stops at prompt files and rules configs. It should start one layer deeper — at the architecture the agent is generating into.
Read →Milan Jovanovic's Pipeline Pattern walkthrough names a failure mode every .NET developer has encountered: business rules that accumulate into an unnavigable service class. Here is what the pattern solves, and why some codebases never need it.
Read →Andrej Karpathy named the evolution at Sequoia Ascent 2026: the developer designs the loop, the agent writes the code. That framing carries an assumption most teams haven't examined — that designing the loop is a skill their team actually has.
Read →Gergely Orosz connected Meta's latest SEV-0 outage to their aggressive AI coding push — and identified a pattern: more outages, not faster features. That pattern has a structural explanation.
Read →A template shows the structure. A code footprint shows the structure populated — at production scale, by real business logic across 15 modules and 524 endpoints. In the AI era, that distinction determines whether your agent generates coherently or just generates faster.
Read →AI coding tools make it possible to generate more software faster than at any point in history. They do not make it possible to skip the architectural decisions that determine whether the software survives production. When you skip them, the debt accumulates at AI speed.
Read →Most .NET modernization projects stall not because the new architecture is wrong, but because the team underestimates what they're carrying. Here's what legacy .NET actually looks like and what a clean landing target costs to reach.
Read →Technical due diligence has always looked for architectural coherence. In 2026, it has a new question: how much of this codebase was generated without a structural spine? Here's what that means for B2B SaaS founders preparing for a raise or exit.
Read →Andrej Karpathy named the evolution at Sequoia Ascent 2026: agentic engineering, where the developer designs the loop rather than writes the code. The problem is that designing the loop requires something real to loop over. Here's what that foundation looks like.
Read →Simon Willison ran Kimi K3 through the pelican benchmark for agentic tool-calling. The model performs well. What the benchmark tests is the model's side of the agentic equation — not the API surface those agents work against. That's the variable teams should be thinking about.
Read →Ethan Mollick benchmarked GPT-5.6 Pro, Fable, Kimi K3, and Inkling on a generative harbor town task this week. The model rankings shift quarterly. The codebase those models generate against doesn't. That asymmetry is where the real investment decision lives.
Read →AI makes teams faster at building. It does not make it easier to find product-market fit. The real question is what platform is ready when PMF arrives — because the window to capitalize on it is short.
Read →Andrej Karpathy described LLMs going beyond just speeding up existing work — enabling new categories of software development. That shift is real. What most teams miss is what it requires of the codebase those agents work against.
Read →When AI agents generate data access code against 700+ named stored procedures, they cannot write ad-hoc SQL. The procedure is the interface. This is not a constraint on the agent — it is the constraint that makes agent-generated data access safe.
Read →Every team thinks about auth at day one. Almost no team thinks about token rotation, multi-tenant data scoping, background job idempotency, and audit trails — until those are the exact problems blocking production.
Read →Vertical-slice modules were the right organizational unit before AI coding tools existed. In 2026 they are also the right context unit — 15 worked examples of how a feature should be built, from UI to database, that agents can pattern-match against.
Read →Boris Cherny, creator of Claude Code, mapped five stages of AI adoption for software teams on July 16. Most organizations are at Step 1. The bottleneck to moving up isn't the model — it's whether the codebase can support ten agents working in parallel.
Read →Dex Horthy ran a fully automated 'dark factory' — no human review, no architectural oversight — for three months. The codebase degraded so badly that one bug required weeks to trace. Gergely Orosz published the story on July 15. Here is what it means for teams planning to run agents at scale.
Read →OpenAI shipped Sol, Terra, and Luna on July 9 — a three-tier model family with a 5x price spread. The decision this creates isn't which model to pick. It's whether your codebase can route between them.
Read →Martin Fowler's harness engineering framework names what separates teams getting coherent AI agent output from teams that don't. The model is the same for everyone. The harness isn't.
Read →Milan Jovanović is right that microservices impose a tax before they deliver any benefit. But the right alternative isn't just 'start with a monolith.' A code footprint is different in kind — production-proven decisions already made, not a starting shape you fill in.
Read →Andrej Karpathy says AI agents bloat abstractions, copy-paste code blocks, and produce aesthetic messes — and he's stopped fighting it. He's describing what happens when fast generation runs against no structural context.
Read →Gergely Orosz is right that careful AI-assisted development produces different results than 'let it rip.' But there's a variable missing from that framing. AI is a lever. The codebase is the fulcrum. Without one, the lever moves nothing in particular.
Read →At Sequoia Ascent 2026, Karpathy said vibe coding raised the floor while agentic engineering raises the ceiling. The framing is right, but it leaves the most important variable unexamined: the ceiling only rises against something.
Read →Karpathy moved to 80% agent coding and still says his AI writes bloated code he's stopped trying to fix. The thing agents cannot generate is the architecture itself — the decisions about where things live and what 'fits' means in a given system.
Read →Gergely Orosz this week pointed to the gap between individual AI productivity gains and team-level output — a coordination and architecture problem that individual-focused AI guidance ignores. The codebase shape is the missing variable.
Read →Karpathy's one-year retrospective on vibe coding surfaces a clear pattern: where speed compounded into product and where it accumulated into liability. The answer has more to do with the codebase than which AI tool the team used.
Read →Most architectural arguments about monoliths vs. microservices miss the real decision: which architectural shape survives growth without operational overhead? For most B2B SaaS teams, the modular monolith with .NET 8 and Azure SQL is still the answer.
Read →CleenUI ships with 14 vertical-slice modules, each running UI to database. Here is why the vertical slice is the right default organizational unit for a B2B SaaS codebase, and what it changes about how features get built.
Read →Teams running WebForms, .NET Framework, or sprawling stored-procedure codebases aren't facing a rewrite decision — they're facing a migration question. Here is what that migration actually involves and where most teams get stuck.
Read →When a company raises a round or gets acquired, technical due diligence inspects things most teams don't prepare for. Here is what the review actually covers and why a coherent codebase architecture is an asset, not a formality.
Read →Vibe coding gets a prototype running in hours. Enterprise B2B SaaS has requirements that take months to build correctly even with good tooling. Here is where they collide and what the gap actually costs.
Read →GitHub opened Copilot Desktop to every plan tier on July 7, and added OpenAI's Codex as a JetBrains agent provider the same day. When the tool cost drops to zero, the quality variable that's left is the codebase.
Read →xAI released Grok 4.5 on July 8, trained explicitly on real Cursor developer sessions. The behavioral record of how engineers build — what they prompt, accept, and reject — is now primary training material. What this changes for engineers and founders.
Read →Gergely Orosz's AMA take from the Pragmatic Engineer: if you're using AI and life seems a lot easier, ask whether you're trying hard enough. The skill atrophy question has specific answers depending on which skills you're delegating — and the organizational version is harder to detect than the individual one.
Read →Milan Jovanović posted this week on why he'd never start a new project with microservices — listing the distributed system costs that arrive on day one. The advice has been in circulation since 2015. It keeps getting ignored. Here is the production case for why it is right.
Read →Ethan Mollick cites OpenAI's internal usage data: the chatbot era is over and agentic AI is expanding to task domains beyond engineering. The question for B2B SaaS builders is what that AI connects to when it arrives.
Read →Gergely Orosz reports the real Anthropic breakthrough is a cloud AI hooked into ALL internal company systems, not a better model. The implication nobody is stating plainly: the architecture of those systems determines what the AI can actually do with them.
Read →A licensed codebase is only as useful as what it actually contains. Here is what to look for when evaluating a code footprint: breadth, coherence, the primitive layer, and whether the architectural decisions already made match the product you are trying to build.
Read →When AI agents generate code against a codebase that has its primitive layer already decided, they inherit the constraints. Auth middleware runs. Multi-tenant scoping holds. Error handling is consistent. The primitives are what make AI generation safe at scale.
Read →The cost of starting a B2B SaaS from scratch does not show up in the line items — it shows up in what your engineers are building in months one through six and whether any of it is your product.
Read →Vibe-coded entropy accumulates until cleanup costs more than starting over. The ceiling is not a technical event — it is an economic one. Here is what it looks like and when most teams realize they have hit it.
Read →The chatbot era of AI coding is over. Agentic systems are arriving — and the codebase they operate against is the context that determines whether their output integrates or accumulates.
Read →The Pragmatic Engineer's 2026 survey of 900+ engineers found that AI amplifies existing tendencies and patterns. That applies to the codebase, not just the team. The variable missing from every productivity announcement is what the AI was actually working on.
Read →The common concern is that AI coding tools will devalue architectural skill. The actual dynamic is the opposite — architectural decisions made before AI adoption compound through every AI-generated output that follows.
Read →Engineering teams are being told to use AI coding tools. The velocity gains only materialize when the codebase is structured enough for AI to integrate into, not just generate into. The missing piece is always the same.
Read →A vertical-slice module is not a folder of related files. It is a complete system unit from UI to database. Understanding what that means in practice explains why AI tools generate more coherently into a modular codebase than into a flat one.
Read →Beautiful AI-built software isn't about visual polish — it's about coherence. Every piece fits the pieces around it. That coherence is architectural before it's aesthetic, and it starts with what the AI generates into.
Read →The decision to use Dapper + ADO.NET against stored procedures is architectural, not accidental. It's a deliberate choice about who owns the query plan — and in the AI era, it turns out to be exactly the right choice.
Read →GitLab's survey of 1,500+ developers found 78% code faster with AI — but software delivery hasn't accelerated. The bottleneck shifted from writing code to reviewing and validating it. Here's what that means for engineering teams and the founders funding them.
Read →OpenAI previewed its GPT-5.6 model family — Sol, Terra, and Luna — to approximately 20 partners on June 26. The three-tier release changes the cost model for AI-assisted development and puts multi-agent orchestration into the model itself. Here is what it means for engineering teams and the founders funding them.
Read →Most codebase problems that surface in technical due diligence were decided long before the 90-day window. Knowing which ones you can fix and which you can't changes how you build from day one.
Read →AI agents generate what they're prompted for. They don't spontaneously build multi-tenancy, role-based access control, audit logging, or the compliance hooks B2B enterprise buyers require. Those have to be in the architecture before the prompting starts.
Read →Every B2B SaaS build begins from one of three positions: nothing, a scaffold, or a production code footprint. The starting line determines what you're building in month one and what you're still building in month six.
Read →AI agents don't modernize a codebase — they generate against it. When the foundation is legacy .NET, every AI-assisted session inherits and amplifies the patterns already there.
Read →The vibe-coding paradox — AI generates code fast but without architectural grounding the speed compounds debt rather than features — has a resolution. It requires a codebase that was designed before the generation started.
Read →Anthropic made Claude Sonnet 5 the Claude Code default on June 30. The context window is now 1M tokens, and the new tokenizer means the headline promotional price is not a direct comparison to what you were paying before.
Read →On July 1, Anthropic redeployed Fable 5 globally after the US lifted export controls. The 19-day suspension ended with a new cybersecurity classifier, a silent fallback to a different model, and a resolution timeline every enterprise team should build into their risk model.
Read →AWS launched Kiro, a spec-driven agentic IDE that generates formal requirements documents before writing code. It is the clearest industry signal yet that the vibe coding trust problem has moved from discussion to product.
Read →On June 16, SpaceX agreed to acquire Cursor for $60 billion — the largest VC-backed startup exit in history. Cursor's model neutrality now answers to a company with its own frontier AI lab. Here is what changes and what doesn't for engineering teams.
Read →On June 13, the US government ordered Anthropic to pull Fable 5 and Mythos 5 under export controls. Sixteen days later, Fable 5 is still dark. The incident is a case study in a risk class most AI integrations have priced at zero.
Read →Google launched Gemini 2.5 Pro with Deep Think on June 22 and immediately set records on science, math, and reasoning benchmarks. SWE-bench tells a different story. Here is what the benchmark split reveals about how reasoning models fit into a software engineering workflow.
Read →The productivity gains from AI coding agents are real. So is the ceiling those gains hit when the codebase has no architectural spine. Here is what makes the difference and how the CleenUI codebase is structured for agent-first development.
Read →Starting from zero has a cost that rarely appears in sprint planning. Here is what the time actually looks like: building the primitive surface vs. licensing a codebase where it already exists.
Read →Microservices split what should not be split. An ORM adds a mapping layer between your code and your query plan. The modular monolith on .NET 8 + Azure SQL avoids both traps. Here is the architecture and why it holds.
Read →Auth, billing, notifications, file handling — every B2B SaaS team builds these before they reach their differentiator. Here is what the CleenUI codebase ships so that list is already done.
Read →M01–M15 are not stubs. Each module runs the full stack — UI to stored procedure. Here is what a vertical slice actually contains and why it matters for the first sprint.
Read →On June 22, GitHub added Claude as a selectable agent provider in JetBrains IDEs, and announced Copilot's default model switches from GPT-4 Turbo to Project Polaris in August. The model is now an interchangeable configuration. The codebase it acts on is not.
Read →On June 24, Gartner predicted that by 2028, AI coding tool costs will surpass the average developer salary. The prediction is directionally right. What most coverage missed is what determines which side of that curve your team ends up on.
Read →SpaceX is acquiring Cursor for $60 billion. The market is pricing coding infrastructure at multiples most teams don't apply to their own build decisions. Code footprints are a distinct category worth understanding before you default to starting from scratch.
Read →Tokenmaxxing collapsed in May 2026 when companies realized 861% code churn wasn't productivity. Martin Fowler's VibeSec Reckoning followed. The pattern is the vibe-coding paradox: optimize the speed metric, miss the outcome.
Read →Alex Albert at Anthropic says working with Claude feels like managing a team, not using a tool. Ethan Mollick's research says AI skill is people management skill. The implication for B2B SaaS builders: if your codebase has no architectural context, the team has nothing to work from.
Read →AI generates code at the syntax layer. Engineers hold the structure. Martin Fowler and Kent Beck said as much at The Pragmatic Summit in February 2026. Here is what that means in practice for a B2B SaaS build.
Read →Tokenmaxxing promised AI productivity. Code churn went up 861%, and Fortune declared it dead by May 2026. The pattern — fast output with no architectural grounding — is the same one playing out in vibe coding shops everywhere.
Read →.NET 11 Preview 5 ships an MCP server template in the SDK. The scaffold is the easy part — what it exposes about your existing API surface is the more useful finding.
Read →On June 22, Five Eyes intelligence agencies warned that AI-powered cyberattacks are months away. The same day, OpenAI launched Patch the Planet to use AI to remediate open-source vulnerabilities at scale. Here is what both mean for teams building on production software.
Read →Every B2B SaaS team faces the build vs. license question. The math looks different when you account for what actually fills the first three months from scratch.
Read →The Miasma supply-chain worm compromised 73 Microsoft GitHub repositories in June 2026 by planting config files that execute a credential-harvesting payload when a developer opens a repo in an AI coding tool. Here is what happened and what it means.
Read →Most legacy .NET systems weren't built badly — they were built for a different era. The path to .NET 8 is defined by boundary decisions, not big-bang rewrites.
Read →Andrej Karpathy called vibe coding 'passé' in 2026 and proposed 'agentic engineering' instead. For enterprise builders, the distinction isn't academic — it's the difference between a product and a liability.
Read →Technical due diligence on a software company follows a short list of questions. The answers either exist in the codebase or they don't — and the audit takes about 90 minutes to find out which.
Read →Gergely Orosz named the pattern: tokenmaxxing, gaming AI usage metrics the same way teams used to game lines-of-code counts. The real AI productivity signal is what ships — and that depends on the codebase underneath the agents.
Read →GitHub Copilot moved to token-based AI Credits billing on June 1, and developers are burning through monthly allotments in hours. Here is what the shift means for engineering teams and the founders paying their bills.
Read →CleenUI ships 14 production-ready vertical-slice modules — M01 Security through M14 Vendor Marketplace. Here is what each one covers and why the modular monolith shape matters more than the count.
Read →AI-generated code is fast. In enterprise contexts, 45% of it carries OWASP Top 10 vulnerabilities. The paradox is not that AI cannot write code — it is that ungrounded speed accumulates differently than a slow, planned build.
Read →Microsoft shipped VS Code 1.124 on June 10 with Copilot Autopilot enabled by default. When an agent writes files and runs commands without asking, the architectural quality of the codebase it acts on is no longer a nice-to-have.
Read →Templates accelerate the first week. Code footprints change the start line. Here is what the category distinction means and why it matters for every B2B SaaS build.
Read →Auth, multi-tenant isolation, background processing, notifications, and a 524-endpoint API surface. Every B2B SaaS rebuilds these from scratch — unless it doesn't. Here is what ships in a licensed code footprint.
Read →CleenUI's data layer runs on Dapper and ADO.NET against 700+ stored procedures. Here is the reasoning behind that choice and why it still holds in a .NET 8 world where alternatives are more capable than they have ever been.
Read →Every new B2B SaaS app rebuilds the same substrate — auth, multi-tenant, audit, i18n. That work is a tax. Here is what it costs and how a licensed code footprint removes it.
Read →AI coding tools hit walls on legacy .NET monoliths — not because the models are weak, but because the codebase has no structure to read. CleenUI is a licensed .NET 8 codebase AI agents can actually use. The case for modernization just got stronger. cleenui.com/blog/why-ai-makes-the…
View on X →AI agents generate against whatever codebase you give them. CleenUI is a licensed full-stack code footprint: 524 endpoints, 15 modules, production-validated patterns. Scaffolds make agents invent structure. A footprint makes agents follow it. cleenui.com/blog/what-makes-a-cod…
View on X →@davidfowl put this plainly: learning a language to review AI code, not write it. Writing is solved. But what you're reviewing against — whether there's a structural pattern to check against — matters as much. Longer take: cleenui.com/blog/if-writing-code-…
View on X →Read @GergelyOrosz's observation about code reviews fading with Fable — the experienced engineer who stopped reviewing had the right instinct. When review can't scale, the codebase architecture has to become the quality gate: cleenui.com/blog/when-code-review…
View on X →Milan Jovanović built a platform to evaluate .NET code quality beyond correct output. It confirms what vertical-slice architecture gives AI: complete context. CleenUI ships 15 of those modules pre-built. New post on what that means for AI development. cleenui.com/blog/what-vertical-sl…
View on X →