> not totally sure about TDD itself - the "don't write any code without a red test" part I'm not into TDD, but I'm absolutely into "never skip the red phase".

> not totally sure about TDD itself - the "don't write any code without a red test" part I'm not into TDD, but I'm absolutely into "never skip the red phase". After fixing a bug or writing a test, I always revert and repeat the test. Same when testing manually (except for the absolutely trivial). You wouldn't believe how often the test then just passes. It's the hygienic thing to do. It's so easy to fool yourself. About half of the time I realize my test (or my dev setup) was wrong. The other times I learn something important, either that I didn't fully understand the original problem, or my bugfix.