It can be taken too far, of course, but the amount of bad code and misleading comments in most systems is substantial. On a different company, two of our teams had a competition every Sprint to see who could take out the most code...
Completely agree. It was a little tongue-in-cheek, but actually removing code and the complexity and tech debt associated with it is incredibly valuable.
Especially if more experienced and knowledgeable engineers can remove the code paths that are "in use" but shouldn't be - premature optimizations that can be simplified, redundancies that can be eliminated, features that aren't bringing in value. It's usually an underappreciated job but can lead to greatly improved velocity and significantly less fragility.
readthenotes1|1 year ago
pressbuttons|1 year ago
Especially if more experienced and knowledgeable engineers can remove the code paths that are "in use" but shouldn't be - premature optimizations that can be simplified, redundancies that can be eliminated, features that aren't bringing in value. It's usually an underappreciated job but can lead to greatly improved velocity and significantly less fragility.