Design debt
in progress
Michael Kunzmann
Our team is working on a giant product with massive tech debt. However, we wouldn't consider function name lengths etc. really to be technical debt. For this stuff, we use TSLint/ESLint and that works quite well.
What really hurts us is keeping track of DESIGN debt (mostly domain-specific): Modularization, code dependencies, ... all this things can't be tracked automatically.
Is there a way to manually "add" debt for design debt, e.g. by adding a comment to the code?
The other thing is that only half the people use VSCode, so a command line tool would be great as well.
Nick Omeyer
in progress
We're currently working on an update that should allow engineering teams to track & discuss design debt (or as we call it, architectural debt).
Please reply here or book a call with me (https://app.hubspot.com/meetings/nick253) if you're curious to see work in progress and would like to shape our solution 😄
Nick Omeyer
Hey Michael, thanks for reaching out!
Currently the way to do what you mentioned would be to use the impact / effort estimates and the improvement notes to flag functions involved in design debt. This would put these functions in the backlog that you can review with your team periodically and discuss how to chip away at this design debt bit by bit.
Let me know what you think, really curious to hear whether that would fit your use case and your team's workflow.
Noted about the CLI — it's something we have in mind but unfortunately haven't been able to get to.