Writing tests before the code can have advantages. Specifically, it forces you to look at what the code's external interface is, rather than how it will be impl

Writing tests before the code can have advantages. Specifically, it forces you to look at what the code's external interface is, rather than how it will be implemented. This is important, because the simpler the interface is, the less cognitive load it puts on someone using it, even if that person is yourself. But I agree that being dogmatic about requiring all code to have tests written beforehand is silly. Being dogmatic about most things is silly.