nmeans

4 ms·

1. 1.▲
   by nmeans 19y ago

   When you've got 30,000 lines of code, you don't always have time to go back through and read all the code to make sure that the particular change you're making doesn't have drastic effects somewhere. Writing good tests means you don't have
2. 2.▲
   by nmeans 19y ago

   If you've got good coverage, you'll have a great chance that they will. You've got to actively monitor your coverage though. As far as backups go, a backup is only as good as it's age. If a startup is struggling to decide if they've got t
3. 3.▲
   by nmeans 19y ago

   If you have humans writing code for you, tests are an imperative. Without tests, one seemingly small code error can wipe out a smatter of user-created data accidentally. Sure, it's worse case, but it could also mean lights out for your st