All that really matters is that it runs… right?
This is what a Principal Engineer’s codebase actually looks like — a live, unscripted walkthrough of iching.rocks. This post was generated with an assist from Claude, querying my self-hosted Engram MCP server against the live iching.rocks repository — itself a demonstration of the semantic-memory infrastructure described below. Nothing here is hypothetical; every snippet was pulled […]
Most people treat “AI-assisted development” as a speed story: more code, faster. The part nobody talks about is what fast actually costs you if nothing is checking the work — silent asymmetries, tests that lie, features that should never have shipped in the first place. Using my Continuum process, I just finished the iching.rocks MCP […]
Most MCP servers ship with a static bearer token. It’s one line in .mcp.json, it works on day one, and it’s the wrong answer the moment your server is anything other than a personal dev tool. Engram, the semantic memory layer behind my AI-native development workflow, started there too. A shared bearer header in .mcp.json, […]
When I wrote about replacing HighRadius in six weeks, I said the pace wasn’t raw AI speed — it was contextual continuity. Every agent session opened already knowing the architecture, the prior decisions, the history. Nothing was re-explained. Nothing was lost. That continuity layer now has a name and a front door. It’s called Continuum, […]
Most people treat “AI-Native development” as a productivity story. Write faster, debug faster, ship faster. That’s the small version. The larger version is this: with the right architecture and process discipline, a single developer can design, build, document, and validate an enterprise-grade platform in a timeframe that would be implausible otherwise. Not a prototype. Not […]