To me Python is fast just like not writing tests is fast.

for prototypes and MVPs time-to-learning and time-to-market are king, and programmer time is the most expensive thing. in that niche Python is helpful and tests just slow you down

tests are super helpful and wise in any sort of long term or safety-critical software, obviously

so, tests (and Python) are not inherently a win or a loss. they just give you different trade-offs

times to write testless Python and times to write test-heavy Go, Rust etc.

Generally I believe in engineering tradeoffs but I think some tests are always important. Even with MVPs. Writing test might double your time to market, but they will allow you to move faster and make less regressions once in production. The early days are some of the least stable features wise and having tests in place to verify things when massively changing a codebase is nice. Also, it can greatly help add confidence to newcomers who don't know the codebase.

understood. theres def an art to judging when its too early to write tests vs the perfect time. its easy for anyone to recognize once its become "too late" and therefore more painful and costly to add it than otherwise would have been

I therefore try to put each situation quickly into 1 of 3 buckets then move forward on that basis:

1. heck no

2. heck yes

3. either way. a gray area

I generally see a case 1 and 2 with confidence. therefore by a process of elimination, that also lets me deduce when its case 3. and in those cases you cant go wrong. :)

"Impossible to predict, the future is." - Yoda

It's interesting because even FANG companies can't agree on testing. I've heard Facebook and Google are very different in this regard.