Re:Using Technical Debt in Your Favor
by noxToken on Thursday March 22, 2018 @09:47AM
(#16648579)
How do you measure complexity with an objective number? I have a few ideas for what could go into it for a given task or process (number of branching paths, number of methods called, LOC, time to develop, etc.) but how do you assign weights to these?
[ Parent
| on HN ]
Re:Using Technical Debt in Your Favor
by humanrebar on Thursday March 22, 2018 @10:28AM
(#16648924)
> ...how do you assign weights to [metrics]
To start with, you don't. Baseball managers and scouts look at a lot of metrics: runs, hits, walks, OBP, VAR, number of pitches in a career, convicted felonies, etc. But at the end of the day, there are people making judgement calls. They're just, ideally, exceptionally well-informed people.
So what I'd like to see, at least initially, is a healthier universe of metrics we can automatically grab from code bases. Deciders can set up dashboards or reports for those as needed. There would still be actual conversations and decisions involving actual humans, but they'd be looking at this data as they're having qualitative discussions about their options.
https://en.wikipedia.org/wiki/Cyclomatic_complexity
(relevant, not a complete answer by any stretch)