Ask HN: How many LOC are you personally responsible for?

Re:Ask HN: How many LOC are you personally responsible for? by okayVGA on Sunday February 02, 2020 @01:39AM (#22215535)

That's a fair comment but I do feel it's a good enough proxy to gauge responsibility. There's also no other metric available that's any more concise.

I figured maintain to cover having originally written it and are charged with its ongoing use.

[ Parent | on HN ]

Re:Ask HN: How many LOC are you personally responsible for? by unlinked_dll on Sunday February 02, 2020 @02:38PM (#22218880)

I feel like you'd want to create an index that's something like (number of features) + (number of unit tests)^2 + (number of adjacent integration tests)^3

And maybe normalize for each by the lines of code for each component and some constant factor after twiddling.

Basically LoC by itself is meaningless. When you gauge responsibility you want to look at how many features are owned, how complex those features are (unit tests) and how critical those features are to the system/product (integration tests). With complexity/criticality being weighted much higher than feature count.

Of course like all metrics this is easy to game. But that's what code review is for.

[ Parent | on HN ]