4 ms·
While it's true that we spend more time in the code than in issue trackers, the advantage of the issue trackers is that a discussion can happen with arguments o
by rakoo 7y ago
While it's true that we spend more time in the code than in issue trackers, the advantage of the issue trackers is that a discussion can happen with arguments on both sides and a final decision can be taken, along with a plan to do it.
Every time I see a conversation in comments like this:
// TODO (mr): Make this more generic
// rp: we only use it once, why change it ?
// ol: I agree with rp
It feels too weird to leave in place. Should I add a comment with my point of view ? If the function in question is modified such that the comments are invalid, should I delete the comments ? Leave them for "documentation" ?
- sergioisidoro 7y agoThat's a very valid point. I was thinking from the perspective of the people contracting the debt. Usually you know what you would need to do if you had time and resources. But yes, for finding existing and uncharted tech debt items, and deciding on their future, the discussion should happen somewhere else.