3 ms·
Tests tests test. Did I say tests? Every kind of tests. When you build a new feature, IMO, its ok if 80% of your time is spent writing a test for a first pass
by softwaredoug 5y ago
Tests tests test. Did I say tests? Every kind of tests.
When you build a new feature, IMO, its ok if 80% of your time is spent writing a test for a first pass crappy solution. (Good) tests make it easier to refactor.
Dealing with legacy code?
The art is knowing HOW to introduce tests. Outside in is the best way IMO. Start with end to end tests, testing the system at well-defined stable interfaces like external APIs. Then carve up the most important internals first.
Also you always have tech debt FWIW. There is no time where it’s profitable to have zero tech debt anywhere. We have to prioritize our investments in the highest priority areas of our code.