I'm not a zealot for it, but test driven development does shorten the feedback loop in significant ways. You get specific feedback for problems and avoid making

I'm not a zealot for it, but test driven development does shorten the feedback loop in significant ways. You get specific feedback for problems and avoid making the same mistakes twice. When I'm working with code that doesn't have it, runtime errors significantly lengthen the time between insights, as I hunt for the root cause of some bug. The general point is that you do better work in small increments and revisions than you do, like Coleridge, getting high and watching masterpieces spill out of you, like Kubla Khan. You will be less sensitive to small things destroying your work, like Coleridge's visitor. Truish story.