4 ms·
It would also be interesting to plot the number of TODOs against the size of the code base too. One would assume that as a project grows, the number of outstan
by jsmcgd 5y ago
It would also be interesting to plot the number of TODOs against the size of the code base too. One would assume that as a project grows, the number of outstanding TODOs would grow too. Where and when this isn't true, might reveal something more interesting.
- WrtCdEvrydy 5y agoWe took some action on this internally at a place I worked. We had a couple of projects that had unit tests neglected so we enforced that you had to round up to the next closest 1% on the package.json for your merge to be approved (as well as adding some unit tests) In 3-4 weeks, code coverage slowly went from 20% to 73%.
- hinkley 5y agoI bet it's more to do with rate of growth than total volume. I believe that one of the cognitive dissonances with people who think a lot of code is good news is that they become overwhelmed by how much they would actually write if they stuck to their convictions and so they start using TODOs to make themselves feel better about doing the wrong thing. Projects that grow slower I suspect have fewer TODOs.