3 ms·
This goes back to the tying of a SQL query directly to profits. That would be an interesting story if it were true, but such a story is probably an extreme rari
by Klinky 6y ago
This goes back to the tying of a SQL query directly to profits. That would be an interesting story if it were true, but such a story is probably an extreme rarity.
We're talking about calculating the impact of your weekly or daily work directly to profit generation. There is a level of granularity and detail to your claim that is likely impossible to realistically calculate, so it would be very hard to accept such claims at face value.
- dfcowell 6y ago"I made the query for X, an operation that is performed Y times per day, Z% faster resulting in N% increase in Xs performed daily. This meant we could (defer hiring additional headcount|do more <profit-generating/cost-limiting process dependent on X> per day)." Many teams don't invest in the tooling required to measure this kind of impact, but it's possible to ballpark it.
- ryandrake 6y agoThat’s a good example. The math doesn’t need to be precise, and you don’t need to track it down to lines of code. “Part of team of X developers who delivered product Y that produced $Z in revenue.” is enough for anyone to very roughly ballpark-estimate impact.
- Klinky 6y agoThis is counter to GPs initial point, where there is a specific claim of direct profit generation. The advice is now just getting watered down into vague ballpark estimates and tossing in a revenue number onto your resume. The advice might as well just be "work on successful projects", which is "thanks captain obvious" advice.