[ryanjshaw]

Is this even a bug or just a case of "in version 0.1 we'll do this quick & dirty", i.e. unaddressed technical debt?

I make a point to keep track of all technical debt in my projects so that I have an easy way to quickly identify opportunities for improvements when there is spare capacity, and also so that technical debt isn't left unaddressed.

[mkopinsky]

How do you keep track of the technical debt? Ticket system?

[kybernetyk]

    //TODO:

    //FIXME:

;)

[evincarofautumn]

Wink all you like, but I get a lot of value from greppable, well written fixmes directly in the source they pertain to. If I’m working on a feature and I discover some odd misbehaviour, there is often a comment right there in the source, explaining precisely what I need to do next.

[bigtunacan]

Agreed. A # TODO: or # FIXME: lives in the code for all to see. I use ticketing & project management tools as well (Pivotal, Trello, others), but these tools are more useful for "X needs implemented and has measurable priority or Y needs fixed ASAP".

Things that we know need to be addressed, but the priority level is "when we have time" are better served living in the code. They tend to get lost in project management and ticketing systems, whereas they live until the code dies if they are in the code.

[GoodIntentions]

If it is something expedient and thoroughly embarrassing I use

//kludge

[bglusman]

Shameless plug: https://github.com/bglusman/debt_ceiling

[varjag]

No need to track it, just default on the debt when it's too much to bear.