The energy threshold for adding a new unit test to the suite and a new row to the docs are vital for it to be done.

If I need to install pandoc to test compile a doc change before i submit it for code review with 3 other maintainers, id rather keep my note or useful screenshot to myself.

If i need to create a c binding of my function so that pytest can run it through 50 rows of cryptic CMake, I'd rather do happy testing locally and submit it as a "trust me bro".

Good and fast international tooling matters massively for good software. And it all comes back to speed and iteration loop.

On top of that, slow meticulous work can then be done. 100% test coverage, detailed uml diagrams describing the system, and functional safety risk analysis matrix documents.

So speed and slowness supplement in different levels of analysis.