News for hackers. Stuff that matters.
Re:Keeping track of technical debt in source code by jwineman on Friday April 14, 2017 @10:32AM (#14114653)
A good way to minimize technical debt is to block PRs that have TODOs until the author completes them, therefore eliminating the technical debt they would have otherwise introduced.
Re:Keeping track of technical debt in source code by crusso on Friday April 14, 2017 @10:39AM (#14114703)
Although I wonder how much self-censorship that encourages. Whether or not to put a TODO in your code is a judgement call. If you tell some developers that admitting to a TODO means that they can't submit, they might not admit to them as often.

It's a bit case-by-case, but I think I'd rather encourage contributors to admit to the lacks in their code and accept them - but get them to commit to follow ups that will fix the problems.

Re:Keeping track of technical debt in source code by abraham on Friday April 14, 2017 @10:48AM (#14114754)
This is likely to lead to developers just leaving out the TODOs instead of doing the work. Especially for work that isn't needed now but should be done at some point in the future.
Re:Keeping track of technical debt in source code by bobbytherobot on Friday April 14, 2017 @11:00AM (#14114837)
You aren't blocking technical debt, you are simply blocking TODO comments.
Re:Keeping track of technical debt in source code by DenisM on Friday April 14, 2017 @10:48AM (#14114753)
You're killing the messenger.
Re:Keeping track of technical debt in source code by softawre on Friday April 14, 2017 @01:39PM (#14115813)
You should go be a team lead, get some deadlines - and the perspective that comes with it.
Re:Keeping track of technical debt in source code by aero142 on Friday April 14, 2017 @11:31AM (#14115021)
How's that job you work at without deadlines and where engineering is the most important department?