Category: Studies

Most of what gets built on my desk now is AI-assisted. Some of it is code I can read but couldn’t write. The way I see it, that only works one way — the discipline around the tool has to be stronger than the tool. Here’s what that discipline is, and the missteps that taught…

I ship AI-written code into a repo that senior engineers review. I can read it — I couldn’t have written it.

Dan North has a pattern called spike and stabilize. Instead of deciding up front whether you’re writing a throwaway prototype or production code, which means deciding at the moment you know the least, you spike to learn, then stabilize what turned out to be worth keeping. Liz Keogh has written a lot of the clearest…

You define the problem. You run the research, make the calls, build the prototype, write the requirements. You hand it off.