Re:Effective Engineer – Notes
by guelo on Thursday December 28, 2017 @02:30PM
(#16024246)
I don't think so. Leverage has a precise concrete meaning in this article. We shouldn't avoid a descriptive accurate term just because it's for an abstract higher-order concept.
[ Parent
| on HN ]
Re:Effective Engineer – Notes
by IronKettle on Thursday December 28, 2017 @02:37PM
(#16024308)
> Leverage has a precise concrete meaning in this article.
Er, not really. From the article:
> Leverage = Impact Produced / Time Invested
"Impact Produced" has a precise, concrete meaning?
Sure. For software, it might be reuse of a component. Reuse leverages existing code. This is precise, unambiguous, and frankly uncontroversial.
Re:Effective Engineer – Notes
by IronKettle on Thursday December 28, 2017 @02:43PM
(#16024353)
> it might be
> This is... unambiguous,
:)
Re:Effective Engineer – Notes
by davidjnelson on Friday December 29, 2017 @05:44PM
(#16032541)
How about revenue or moving the needle on a key business metric like churn or order flow conversion rate.
Re:Effective Engineer – Notes
by brucephillips on Thursday December 28, 2017 @03:47PM
(#16024765)
"Synergy" is a precise term as well.