3 ms·
> I'd recommend prioritizing getting those numbers. I'm also at Google. I know a few L7s/L8s who lead these sorts of engineering productivity teams and organiz
by UncleMeat 6y ago
> I'd recommend prioritizing getting those numbers.
I'm also at Google. I know a few L7s/L8s who lead these sorts of engineering productivity teams and organizations. It isn't just that they aren't prioritizing getting precise numbers. It is that the entire industry has very little idea how to measure engineering productivity. This is a stupendously difficult problem and an area of active research.
The metrics you describe here are okay (build times are easy to measure and can be directly valuable) but they really do represent a limited view. They don't capture all sorts of important stuff. What is the measured value of transitioning to a new C++ version? What is the measured value of best practices documentation and training courses?
Measurements are stupendously valuable when they are feasible and meaningful. But there is real work that should be done that is almost impossible to convert to numbers, let alone dollars.