News for hackers. Stuff that matters.

A comment on Keeping track of technical debt in source code. Parent comment

Re:Keeping track of technical debt in source code by Johnie on Friday April 14, 2017 @12:38PM (#14115438)
At Google, the team that I worked on required the format `// TODO(name): [Tracking Bug#] comment `

In other places, I've seen just blanket `// TODO: comment` is pretty bad. There's no accountability and also you don't know when it's obsolete.

[ Parent | on HN ]
Re:Keeping track of technical debt in source code by hinkley on Saturday April 15, 2017 @02:04AM (#14119623)
Sometimes the TODO message doesn't make enough sense, and having the author gives you who to ask for context.
[ Parent | on HN ]
Re:Keeping track of technical debt in source code by koverstreet on Saturday April 15, 2017 @07:47AM (#14120382)
That's what git blame is for

(I've got a thing in vim that runs git blame on the current line, and pops up the commit message in the quickfix window).

[ Parent | on HN ]
Re:Keeping track of technical debt in source code by hinkley on Saturday April 15, 2017 @11:32AM (#14121140)
Git blame only works until code starts shifting around.
[ Parent | on HN ]