Stream: t-compiler

Topic: tracking technical debt?


mw (May 09 2019 at 11:05, on Zulip):

There's lots of talk about technical debt in the codebase and I definitely feel it's weight when trying to modify certain parts of the code. But do have a place yet where we actually collect concrete issues in a structured way? Having something like that seems like a good first step for planning potential improvements.

oli (May 09 2019 at 11:17, on Zulip):

we have the cleanup tag on github

oli (May 09 2019 at 11:17, on Zulip):

we could tag all issues as such and link to a filtered search

mw (May 09 2019 at 11:19, on Zulip):

that would be a start. Although cleanup sounds too harmless, in my opinion :)

oli (May 09 2019 at 11:20, on Zulip):

we can rename it to technical-debt :D

oli (May 09 2019 at 11:21, on Zulip):

also https://oli-obk.github.io/fixmeh/ for in-source technical debt

nikomatsakis (May 09 2019 at 12:23, on Zulip):

It's a good question.

nikomatsakis (May 09 2019 at 12:23, on Zulip):

I feel like it would be nice if we could loosely write down "things that were hard"

nikomatsakis (May 09 2019 at 12:23, on Zulip):

Something lighter than github issues / FIXMEs,

nikomatsakis (May 09 2019 at 12:23, on Zulip):

i.e., if we don't know the answer yet =)

Last update: Nov 22 2019 at 04:30UTC