[xandrius]

Exactly! I've myself spent days investigating an issue only happening on a specific Android device (but used by an important client) only to find that the solution was something along the lines of using "opacity: 0.1" instead of 0.

That bug was left unfixed for months but now it's solved. Should I have received a talk because of that?

(Of course the commit would have had at least 10 LOC more, explaining the reasons and providing references to future devs/self)

[khazhoux]

> Should I have received a talk because of that?

Of course not.

But, if your commit history for last 6 months is just one or two of those one-line changes a month, that might hint that there’s a problem.

[mdp2021]

That makes your point clear, but then what you are looking for is not a scalar value (that may be for instance be subject to a proportional judgement) but a fuzzy threshold.

[Moru]

This is exactly why KLoC is not a good measurement. If you know about this, you will make sure you match everyone else by embellishing your line count with comments, copy and rename functions or extra deep nesting. The manager will still not know anything without looking at everyones code.

[khazhoux]

A good manager should look at everyone's code.

A good manager should recognize that if a developer does nothing but annotate code with comments, and that's not what they're expected to be doing, there's a problem.

[Moru]

Ofcourse, but if the manager is using the KLoC to decide who to look at, that won't happen.

[eviks]

Might that hint that the problem that is there is that the metric is bad?

[khazhoux]

So if you managed a team, and when you look at commit histories you notice that one person has <1 commit a month and you look at the commits and they're trivial... you would disregard any concerns?

[xandrius]

The answer is still "it depends", I would imagine that issues would arise well before you had to look at their commit history.

I believe that if you are a good manager, you would just need to look at what tickets get done during the sprint and that's it. If you complete your tickets and pass QA/UAT in 10 LOC, so be it. There is no need to micromanage.

[jen20]

I would wonder how it got to the second month, certainly - getting to the point where this kind of post-hoc analysis can actually be done is a serious failing of management.

[rsynnott]

I mean, seems highly role-dependent. If, in practice, your role is to investigate and fix very difficult problems, that’s precisely the sort of commit history one might expect.