I think unit testing, property based testing, TDD, and the like are valuable and I can’t imagine doing development without them, I consider it good engineering.

I think unit testing, property based testing, TDD, and the like are valuable and I can’t imagine doing development without them, I consider it good engineering. In fact I always make sure to write good tests even for interview take home tests etc. I’m providing this background because I’m still fairly wound up by a terrible interviewing experience I had with the only company so far that specifically mentioned TDD and made a big deal about it. I’ve never experienced such a farcical technical test. It was an hour, and the interviewer (only one, red flag already as it allows for bias) spent twenty minutes debating the name of a single test and kept circling back to the topic when I tried moving past it. Kept making a big deal about “TDD test names”. Refused to let me write anything. Refused to elaborate on any requirements or even what he really wanted me to do. After the hour was up I’d written one working test and one broken test. The actual system under test was a one line method, because he spent another fifteen minutes getting angry that I wanted to even run the test. Absolutely ridiculous and it’s unfortunately made me very wary of anywhere that makes a big deal about TDD despite being a big proponent of testing myself. So yeah, if that’s people’s exposure to TDD I’m not surprised some people don’t like it. If you’re ever interviewing for a UK based company that works in the arts and theatre booking space that mentions TDD, run a mile.