Stop reviewing code. Start defining "done".
If the last post was about letting go of the code, this one is about what makes letting go safe. Engineers have always wrapped unreliable components in guardrails. AI is just the next one.
read →The tools are ready. Your team is not.
The first two posts were things one engineer can do alone. This one is not. Part of it is what I have seen so far, and part of it is where I think this is heading and what I am still trying to get right.
read →