News for hackers. Stuff that matters.

A comment on The McNamara fallacy: Measurement is not understanding. Parent comment

Re:The McNamara fallacy: Measurement is not understanding by andrei_says_ on Tuesday February 01, 2022 @07:05PM (#30171649)
The issue is that the bean counters count beans and not creativity.

Can we think of a way to connect and individual’s creativity to money flow?

As an engineer I am most productive when I solve a business need without writing code. How can I associate my contributions with measurable profit?

[ Parent | on HN ]
Re:The McNamara fallacy: Measurement is not understanding by bb88 on Wednesday February 02, 2022 @12:57AM (#30174280)
When you write an api, add "dollars_saved", for the amount of dollars your api is currently saving the company. CFO's love that quantitative shit.
[ Parent | on HN ]
Re:The McNamara fallacy: Measurement is not understanding by salawat on Wednesday February 02, 2022 @09:56AM (#30178378)
Y'all are looking for quantitative Quality measures. Good luck. If you aren't sitting on top of Spend informed by actual company history, you're hosed, and most places are hush hush af about that.
[ Parent | on HN ]
Re:The McNamara fallacy: Measurement is not understanding by nickpeterson on Tuesday February 01, 2022 @07:46PM (#30172005)
Code and documentation are debts, Features divided by lines of code is a good metric.
[ Parent | on HN ]
Re:The McNamara fallacy: Measurement is not understanding by rocqua on Wednesday February 02, 2022 @02:44AM (#30174867)
Dear god.

Once that metric becomes anything close to a target the monstrosities it would bring ae horrific!

[ Parent | on HN ]