I'm ambivalent about testing. I've no fear of not writing tests for something small or scrappy. But.. when I've persevered, weeks into a project they've saved my ass more than once and I've been able to recognize situations where a bug would have previously forced me to spend hours debugging or to release broken software.

TDD isn't a one size fits all technique. But just because it takes time, doesn't always yield immediate benefits, and can leave a bad taste in the mouth at first, it doesn't mean you wouldn't ultimately benefit (even beer shares these negatives ;-)).

The great thing, though, is that there are so many ways to practice testing. If you don't want to go with full on "test first" TDD practices, even rolling out a handful of automatic integration tests could cover your most onerous painpoints (this is my strategy on old projects that have no tests - something's better than nothing). Though TDD's proponents foam at the mouth about always testing, it's not a binary option - you can wade in the shallow end and get into deeper waters over time as it begins to click.