Talk:Technical debt/Flow

I just finished writing a rant on technical debt: User:Daniel_Kinzler_(WMDE)/Avoiding_the_Tech_Debt_Trap. It would be great to get feedback on it. Perhaps some of the things I mentioned there could be incorporated into this document.

Debt accumulating in our user interfaces is created by similar means as technical debt in code: Unclear direction, undocumented decisions, pressure to meet deadlines… It is also impossible to refactor without affecting (end)users.

I wonder if we should include this kind of debt, too (since many of the causes and effect follow a similar pattern) or if we might create another discussion on it (since it has some unique features and represents itself in UI, not code)

Totally agree.

@Jdlrobson – do you have also an opinion on include-here vs. start-somewhere-else?

Why would we not include it here? I believe UX debt and technical debt are very close or related in certain situations. It would get confusing.

For instance Minerva's use of MediaWiki UI rather than OOjs UI; Wikidata's use of jQuery.UI has elements of both technical and UX debt unless i'm mistaken?