I'm defining what comes after vibe coding. I call it Intelligent Engineering.
That's why the backlog is still growing. We're entering a new era I call Intelligent Engineering. This is where AI doesn't just generate code. It operates inside your architecture, your backlog, and your standards. The companies that get this right will compound faster than everyone else. The ones that don't will watch AI build their next decade of tech debt in months. That's why I'm building DevNitro.
This blog platform was built using DevNitro's autonomous mode in 95 minutes.
Learn more at devnitro.comThis week I gave the agent a language server, so it can rename symbols, find references, and read diagnostics instead of grepping. Plus IssueSwarm epics.
Read moreThis week I used DevNitro to build DevNitro's own tools, matured IssueSwarm into a usable tracker, added recursive context management, and wired up team subscriptions.
Read moreDevNitro's autonomous agent ran a real backlog this week and produced 162 commits building team billing and IssueSwarm data isolation, tokens permitting.
Read moreI pointed four AI models at the same build, Opus, Sonnet, Codex, and Ollama, and watched each one fail differently. Plus subagent orchestration and testing.
Read moreThe week DevNitro started generating working sites: 22 hours on the create-site tool, real-time tool-call visibility, and API versioning across the platform.
Read moreI've spent 29 years building software. From game development books to Fortune 500 systems to mixed reality with HoloLens. Every era taught me something about how engineering teams actually work. Now I'm applying all of it to what I think is the biggest shift yet.
More about me