Thanks for the interesting perspective. I've tended to be rather skeptical of the strict TDD every-project-must-have-100%-test-coverage mindset myself. For bri

Thanks for the interesting perspective. I've tended to be rather skeptical of the strict TDD every-project-must-have-100%-test-coverage mindset myself. For bringing some value back into automated testing, one guy I worked with thought that usually the tests themselves aren't that important, but instead what was beneficial about an automated testing mindset is that it forces you to architect your code well, into small, modular pieces with carefully specified cross-dependencies. I will also say that I've found Git to be very beneficial for some types of hobby projects. Particularly the kind where you end up deploying the result in many places. Like if you're toying around with an Android app, it's nice to know exactly what version of the app is on this emulator, that emulator, your main phone, your tablet, your spare test phone, etc. That's why I find it useful to maintain a Git repo for it, carefully and religiously commit every new feature to it, and create a build system that tags the built files with the current Git commit somehow.