Talk:Technical debt

About this board

Avoiding the Tech Debt Trap

1
Daniel Kinzler (WMDE) (talkcontribs)
Reply to "Avoiding the Tech Debt Trap"

UX debt – include or discuss elsewhere

4
Jan Dittrich (WMDE) (talkcontribs)

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)

Jdlrobson (talkcontribs)

Totally agree.

Jan Dittrich (WMDE) (talkcontribs)

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

Jdlrobson (talkcontribs)

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?

Reply to "UX debt – include or discuss elsewhere"
There are no older topics
Return to "Technical debt" page.