Goldman Sachs updated its internal AI coding tool policy in October, limiting Claude Code and GitHub to its ~12,000 engineers. The stated reason is risk management. The underlying reason is structural.
Read →Andrej Karpathy named the next step beyond vibe coding: agentic engineering. What he didn't specify is what the engineering substrate needs to look like. Multi-tenant scoping, audit logging, compliance hooks — these have to be in the codebase before the AI session starts.
Read →Technical due diligence in 2026 has a new dimension. Acquirers and their advisors now understand AI-assisted development well enough to ask whether the codebase under review supports it or fights it. The answer changes the risk profile of the acquisition.
Read →Vibe coding at the individual level is a speed story. At team scale, it becomes a coherence story — three developers, three AI sessions, three different patterns for the same cross-cutting concern, one codebase that no one fully understands.
Read →When AI makes all new code disposable and write-only, technical due diligence shifts its focus. It's no longer reading the code. It's reading the architecture.
Read →Andrej Karpathy defined agentic engineering as coordinating fallible agents while preserving correctness, security, and maintainability. For enterprise B2B SaaS teams, that discipline starts in the codebase, not the process document.
Read →Technical due diligence doesn't inspect features. It inspects structure, consistency, and whether the codebase has a design or accumulated one — and those are different things to prepare for.
Read →Ethan Mollick argues that Forward Deployed AI Engineers won't deliver what companies hope because AI adoption is fundamentally an organizational design problem. He's right about the org layer. The codebase coherence layer below it — whether AI tools have patterns to generate against — is what most teams haven't named.
Read →87% of Fortune 500 teams have adopted at least one vibe coding tool. 29% of developers trust the code AI produces. The gap isn't adoption — it's that most codebases weren't designed to be AI-augmented at enterprise scale.
Read →A codebase can serve real customers, generate revenue, and still fail technical due diligence. The diligence question isn't whether the code works — it's whether an unknown engineering team can maintain, extend, and scale it under conditions the acquirer can't predict. That's a different bar.
Read →Ethan Mollick calls AI adoption decisions organizational design, not IT choices. He's right about the org layer. But there's a structural layer beneath it most teams haven't recognized: the architectural decisions in your codebase are already an AI policy.
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 →Configure a demo environment in about twenty seconds — theme, spacing, the modules you care about, sample data for your industry — then launch the full dashboard in your browser. Nothing to install, no signup.