Topic
5 articles found
The brief was approved. Scope defined, questions closed, acceptance criteria written. The obvious move was to start building. I ran the Plan phase first. Planning and the Plan phase are not the same thing. Every engineer plans. Sprint boards. Jira tickets. A rough sequence before a large refactor st
Learn how Jason Liu uses Codex to preserve context, manage complex projects, and help work continue beyond a single prompt.
In software engineering, we understand the concept of a code smell. A single long method is not necessarily a disaster. An untested utility file is not ideal, but it will not crash the server. However, when you combine a long method, global state, and zero test coverage in a critical payment gateway
For a while I blamed the model. The agent would build something plausible and wrong, and I would assume it needed a smarter brain. Then I went back and read the tickets I had handed it, and the problem was obvious. My acceptance criteria were wishes, not specifications. The agent built exactly what
I built a new tool. It is a Level 2 project harness installer (blurs into Level 3). The page is at tacoda.dev/keystone. The repo is at github.com/tacoda/keystone. keystone init drops a markdown harness into your repo. Five layers: principles, idioms, domain, state, process. Plus an activation file t