>In tech, literally every change we make is logged in a history with timestamps.
That only applies to junior developers whose measure is the amount of code they complete and even that is potentially gameable with fluff check-ins.
High-level design by senior developers, writing specifications, and QA, for example, don't have an output that's measurable in kLOC or work per unit time.
Stats are fluffable, but is a fluff check-in really a fluff check-in if nobody actually looking at it can tell it's fluff?
> High-level design by senior developers, writing specifications, and QA, for example, don't have an output that's measurable in kLOC or work per unit time.
They still have measurable, logged and recorded output. Specs get checked in. Bugs get filed and updated. Sample some of it.
This will better help you identify who's struggling or slacking off in the office too.
That only applies to junior developers whose measure is the amount of code they complete and even that is potentially gameable with fluff check-ins.
High-level design by senior developers, writing specifications, and QA, for example, don't have an output that's measurable in kLOC or work per unit time.