What tags do you use in the task list (e.g. Visual Studio 2008)

In our code, we currently use the following tags, which, in turn, can be listed in the visual studio task list:

TODO to indicate the tasks inside the code that need to be completed

// TODO: optimize this loop

HACK, to mark a code that exists only for something to work at the moment, for example, for a presentation

// HACK: assume we know the users password to skip the need for a popup here

REVIEW to mark part of the code that has been viewed and requires some editing

// REVIEW: the following method is redundant, use ABC.DEF() instead

FIXED to mark REVIEW-codesegments corrections that have been fixed so that the observer can see that corresponding changes have occurred.

// REVIEW: the following method is redundant, use ABC.DEF() instead
// FIXED: removed the method and updated the calls

? , ( ) ( 10 )? ?

+3
6

TODO. , . , . HACKs TODO , ?

, subversion , Mantis . - , , , , DIFF .

. , .

+2
// I18N

, , , "" ... , - "".

+1
// SOYLENT:

, , .

0

TODO, TODO , , "" (, NTODO Nick To Do).

HACK , ,

int thisID = list[0].ID; // hack, assume list found a match

.

0

I use TODO to indicate code that needs to be changed or added, and also to display functionality or code that still needs to be executed because it is often forgotten.

I use HACK to determine when I use the code I want to change or something hardcoded. It also indicates areas in which I need to do more research before implementation.

0
source

We use TODO [Initials] [Date], which helps people accountable for their todos.

0
source

Source: https://habr.com/ru/post/1697670/


All Articles