Code gardening: testing and refactoring
We have it implemented but did not put any tests yet. Should we? The answer is always yes. Do we go for 100% coverage? If that 100% is scary as to produce paralysis, then aim for the 20%, and we'll see after that, maybe we will change our minds. Cause we keep talking about "building" code as a static drawing, but it would be more accurate to talk about growing and gardening; the real-world projects are more organic and evolve through iterations and refactorings. The healthiest approach could be not to get too attached to those flowers; they will eventually vanish (when a new colleague arrives ;)
ShortCast #
- Code gardening: testing and refactoring
- Carmen Maymó
- code-gardening
- testing
- refactoring