@gsuberland I have a similar “don’t bother writing tests and setting up linting” rule for side projects now, for similar reasons. I’d be endlessly starting things and getting bored before actually building anything I intended to.
@jon I do usually make a few unit tests for stuff that's non-trivial, because it's much easier to fix a problem when the regression occurs than when I hit a bug several years later and can't remember a damn thing about how it works, and that's also a recipe for my brain going "too much effort, don't bother" (or worse, "JUST REWRITE IT AGAIN BRO!"), but I definitely agree with not doing full TDD and rigid styling when you're just tinkering or prototyping.
@jon although the other approach is just to go harder on defensive development styles, which is my natural way of doing things anyway. lots of validation even if things further up the call stack are supposed to have done validation ahead of time.