Avoid These 35 Habits That Lead to Unmaintainable Code

Re:Avoid These 35 Habits That Lead to Unmaintainable Code by tiagoespinha on Wednesday May 17, 2017 @03:55AM (#14356439)

Normally the argument is the this should be part of your backlog and not spread all over the code where no one (and especially the PO) can keep track of all the TODOs in all the files.

[ Parent | on HN ]

Re:Avoid These 35 Habits That Lead to Unmaintainable Code by Terr_ on Wednesday May 17, 2017 @05:02AM (#14356720)

Depends on trust. I've had an experience where old tickets documenting important architectural problems (e.g. SQL injection) were mass-closed as "probably obsolete" by managerial types.

I was very happy I left a TODO in the actual code calling out the problem, because I could find and reopen the wrongly-closed ticket.

[ Parent | on HN ]

Re:Avoid These 35 Habits That Lead to Unmaintainable Code by piaste on Wednesday May 17, 2017 @06:05AM (#14357003)

Heh. Visual Studio actually does keep track of all the TODOs in all the files in your project. It's the Task List window (View -> Other Windows -> Task List, or ctrl-alt-K).

[ Parent | on HN ]

Re:Avoid These 35 Habits That Lead to Unmaintainable Code by wruza on Wednesday May 17, 2017 @07:52AM (#14357522)

Does it track FIXMEs?

[ Parent | on HN ]

Re:Avoid These 35 Habits That Lead to Unmaintainable Code by TheQwerty on Wednesday May 17, 2017 @08:23AM (#14357695)

By default it looks for the tokens: HACK, TODO, UNDONE, and NOTE.

However, you can add your own tokens and assign different priorities to them.

https://docs.microsoft.com/en-us/visualstudio/ide/using-the-...

[ Parent | on HN ]

Re:Avoid These 35 Habits That Lead to Unmaintainable Code by wruza on Wednesday May 17, 2017 @04:59PM (#14362735)

Very nice, it now almost resembles the functionality of "grep -rn FIXME ." in the shell and ":grep -r FIXME ." in vim.

[ Parent | on HN ]