From Fork to Framework, Part 7: How Claude Code and DevFlow Made This Possible
One engineer, six months, several iterations, 1,400+ commits. Here is how AI-assisted development with structured tooling made that timeline real.
Category
Engineering
Build notes from the AOCyber platform — the stacks chosen, the rewrites survived, and the reasoning kept in.
7 posts
From Fork to Framework, Part 6: ConnectRPC, Eden Libs, and the Framework That Pays for Itself
Protocol Buffers, generated clients, and a shared platform library let us build Eden Circle in eight days. Here is how the pieces connect.
From Fork to Framework, Part 5: Why Flutter Won the Frontend
One codebase for iOS, Android, web, and desktop. Flutter gave us platform parity in four days that would have taken months with separate native stacks.
From Fork to Framework, Part 4: Why Go Won the Backend
Goroutines, sqlc, and 10-megabyte containers. Here is why Go is purpose-built for an LLM gateway and multi-tenant AI platform.
From Fork to Framework, Part 3: Why Rails Almost Won
Rails 8 eliminated Redis, gave us conventions for everything, and let us ship serious security features fast. Here is why we still moved on.
From Fork to Framework, Part 2: The Python and Svelte Rewrite
Our second iteration replaced the forks with a clean-room build using FastAPI and SvelteKit. Feature velocity was excellent. Operational complexity was not.
From Fork to Framework, Part 1: Standing on Shoulders
We started AODex (originally AOCodex) and AOSentry by forking two excellent open-source projects. Here is what we learned about the limits of that approach.