This level of detail isn't really helpful. I am working with AI and genuinely interested in learning more, but this offers very little.
More concrete examples to illustrate the core points would have been helpful. As-is the article doesn't offer much - sorry.
For one, I am not sure what kind of code he writes? How does he write tests? Are these unit tests, property-based tests? How does he quantify success? Leaves a lot to be desired.
What works for me is that often on a Monday I restart my machine. If something is truly important, I save it before the restart. There is something good to start from an empty state.
As an aside, this is the type of a problem that I think model checkers can't help with. You can write perfect and complicated TLA+/Lean/FizzBee models and even if somehow these models can generate code for you from your correct models you can still run into bugs like these due to platform/compiler/language issues. But, thankfully, such bugs are rare.
If you're interested in a tutoring Latin remotely, please let me know. If not, no worries.