TDD was designed to get rid of the dread. You don't even need to write full tests, a checklist helps a lot. But proper TDD should work in seconds. Check out the book by Kent Beck, which explains it a lot better than many articles.
The basics of it is red, green, refactor.
Before you write the code, write the test. Autogenerate the code from the test until it compiles. It will be red (fail) because there's no code. This is how you test the test.
Then do the absolute simplest thing to make the test green (pass). Make it really hacky. Once it passes, refactor (clean up your code).
The positives of this is you don't even have to be in flow. It takes seconds to do a red, seconds to go to green, seconds to refactor. You can be interrupted at any time and not lose your train of thought. If you're writing some tough code, there's also some other techniques you can do, like write several tests for behavior and triangulate the code from that.
The basics of it is red, green, refactor.
Before you write the code, write the test. Autogenerate the code from the test until it compiles. It will be red (fail) because there's no code. This is how you test the test.
Then do the absolute simplest thing to make the test green (pass). Make it really hacky. Once it passes, refactor (clean up your code).
The positives of this is you don't even have to be in flow. It takes seconds to do a red, seconds to go to green, seconds to refactor. You can be interrupted at any time and not lose your train of thought. If you're writing some tough code, there's also some other techniques you can do, like write several tests for behavior and triangulate the code from that.