Starting your implementation with a test that's setting up, what the expected result is, and then implementing the controllers/whatever against that test is pre

Starting your implementation with a test that's setting up, what the expected result is, and then implementing the controllers/whatever against that test is pretty satisfying. In web development it also makes back-end development faster. Switching to a browser, reloading the page and inspecting the console/properties/page, is so slow. I wasn't really into testing until a certain point, but having the confidence that your business logic still works after doing change requests is a bliss. No testing it in the browser, no testing it with postman, no checking if mails are send in your dummy smtp server interface etc. When you don't write software that changes very often or has many use cases, go ahead and leave them out, but the more you take on your shoulders, the better automating the tedious work.