> including writing them all by hand, and push the “this isn’t fun, I’d rather do something else” bits to a minion.

That’s not really the part I’m talking about. My gut says that if tests are a blocker for weekend projects, people just don’t bother writing them. I certainly wouldn’t imagine them taking much longer to code than the core functionality.

In my experience, which seems to resonate with a lot of people, AI quickly stands up really useful boilerplate and very convenient purpose-built scaffolding… but is a lot less useful helping you solve actual problems in a way that makes sense to people that have those problems. Especially if you’re using a less-mainstream language or some other component.

You both have very good points here, but once I get finished with both of the 90% programming times, and everything seems to finally work with no more bugs (and it's true), then for my heavy industry work I look forward to spending 10X as much effort testing compared to coding.