
I stopped trusting my coding agents, so I built a system to not trust them
As it happens, the last year for me was just big projects: Orome.ai , Relayn.sh . Multiple elements, shifting requirements, ever-growing codebases. Even having multiple layers of documentation did not help. I kept losing context, agents kept losing context, and at some point I started wondering if any of us actually knew what we were doing. (Spoiler: the agents did not.) This is about what I built to manage that, and why most of it exists specifically because agents will misbehave the moment you give them an opportunity. History: tools, sprints, and learning the hard way About a year ago I started to take AI-assisted programming seriously. The boost from Cursor and Claude was immediate. Windsurf appeared and then disappeared. I tried to always use "the best tool right now," and I lost an unreasonable amount of time re-calibrating to new tools, re-explaining my codebase, rebuilding configuration files. Lesson one: stop chasing the best tool. Pick one. Get good at it. (I stayed with Curs
Continue reading on Dev.to
Opens in a new tab


