When I read the 7 tool and the abstract, I hope that there is a clear connection of how technical debt mitigation helps to improve the metric results.
Reading the 7 tools, how do I communicate that it is important to track these metrics because it is important to focus on heavy issues. We struggle with everything is a fire and no -technical- person is in charge of triage.
Thanks for the feedback there. The 7 tools are more of lenses for analyzing a particular problem. I plan on showing more persistent ways of measuring code over time - tools like SonarQube / SonarCloud, NDepend (for the .NET world), etc. However, a lot of the aspects of 7 basic tools - if you repeat the exact same experiment later on - you should see an improved result.
I do like your point on firefighting and no one person heads up the responsibility of paying down debt. I will be sure to incorporate that into my talk.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
When I read the 7 tool and the abstract, I hope that there is a clear connection of how technical debt mitigation helps to improve the metric results.
Reading the 7 tools, how do I communicate that it is important to track these metrics because it is important to focus on heavy issues. We struggle with everything is a fire and no -technical- person is in charge of triage.
Thanks for the feedback there. The 7 tools are more of lenses for analyzing a particular problem. I plan on showing more persistent ways of measuring code over time - tools like SonarQube / SonarCloud, NDepend (for the .NET world), etc. However, a lot of the aspects of 7 basic tools - if you repeat the exact same experiment later on - you should see an improved result.
I do like your point on firefighting and no one person heads up the responsibility of paying down debt. I will be sure to incorporate that into my talk.