Me too but let’s play devils advocate here. 1) you likely aren’t going to get the job without some absurd degree of unit testing 2) most of your code should b

Me too but let’s play devils advocate here. 1) you likely aren’t going to get the job without some absurd degree of unit testing 2) most of your code should be pure functions making them trivial to unit test 3) writing pure functions and making your code testable makes your system less coupled which is a good thing 4) designing the tests is designing the software which is often helpful That’s it I don’t have a fifth point. Actually I do, writing software is a form of art and it cannot be summed up as simply as unit testing everything always bad or always good. There might be somethings like converting an engine performance simulation to Golang from Excel that might be fantastic to unit test the shit out of, testing if onPress works on your button component is basically pointless.