News for hackers. Stuff that matters.
Re:The measurement problem in software engineering by lukekim on Thursday December 18, 2025 @02:23PM (#46317272)
Like most things, all measures fail point in time and on short time horizons, but law of big numbers and trends can be useful. I.e. compare yourself (on almost any measure) to yourself in your most productive period.

We reviewed our metrics for period-on-period comparisons at 1, 2, 3, 4 years and the numbers are surprisingly consistent for each person, and across similar productive engineers.

Like in the article, if you can apply a semantic score across years of data, it gives you a pretty good idea.

Re:The measurement problem in software engineering by jbcranshaw on Thursday December 18, 2025 @02:24PM (#46317284)
Curious what you use for a semantic score across years of data?
Re:The measurement problem in software engineering by lukekim on Friday December 19, 2025 @12:54AM (#46322656)
Periodic objectives x customer results then GPT-5 scoring pull requests, etc. against them roughly aligned to that period. I.e. it scores higher if code is used by and produces value for customers.