[nonamegiven]

I'm not one of the people you're looking for, but like so many things, a flexible mix based on the character of the work at hand is usually most effective. Sometimes (sometimes) you doodle to think, sometimes you code to think: how do you write a failing test for doodling?

FWIW I was writing what were effectively unit tests, and doing them essentially first or all but first, in the late eighties before (I think) TDD even had letters, but it didn't rule my life. I was chastised for being too new and not good enough to carve the whole monolith at one sitting. I did what I needed to anyway.