4 ms·
How come fixing bugs to make data pipeline more robust and data more accurate does not fall under "things that are good for the company"?
by gordon_freeman 9y ago
How come fixing bugs to make data pipeline more robust and data more accurate does not fall under "things that are good for the company"?
- kevan 9y agoIt might be good for the company. But the point is you need dollars and cents metrics that prove it is, not just righteous feelings that less bugs is better. Engineers at ground level are often well insulated from the actual business impact of the work they do. Because they aren't given any insight into the business side they instead optimize for measurable metrics like bug count and data accuracy.
- mseebach 9y agoThe point is that it's on you to articulate the value of what you're doing. Some activities are "batteries included" when it comes to metrics, but a great many aren't. If fixing bugs in the data pipeline is indeed valuable to the company, you can explain to the promotion panel how (after all, you convinced yourself).
- dilyevsky 9y agoBecause google has a "technical ladder" document which mentions words "complexity" and "impact" like a dozen times and the word "quality" like once or twice ;-) That document is supposed to be used by promo committees to eval if you are "ready".