News for hackers. Stuff that matters.
Re:What McKinsey got wrong about developer productivity by paulcole on Tuesday October 24, 2023 @11:21AM (#38000420)
> You can't measure any productivity that has any cognitive component

Understanding and measuring productivity can be valuable to a business. Sure they can't measure productivity for some roles as precisely, simply, and accurately as say counting the number of jelly beans in a jar.

But that doesn't mean productivity can't be measured in a way that is useful to the business. There's just tradeoffs involved.

Re:What McKinsey got wrong about developer productivity by distortionfield on Tuesday October 24, 2023 @12:11PM (#38001233)
Anecdata but: In my almost ten years of software engineering engineering, I’ve never once seen an organization deploy developer productivity metrics and do anything useful with them except bludgeon developers that management already don’t like with the number that came out of The Machine ©
Re:What McKinsey got wrong about developer productivity by FireBeyond on Tuesday October 24, 2023 @01:04PM (#38002021)
Obligatory:

"Y.T.’s mom pulls up the new memo, checks the time, and starts reading it. The estimated reading time is 15.62 minutes. Later, when Marietta does her end-of-day statistical roundup, sitting in her private office at 9:00pm, she will see the name of each employee and next to it, the amount of time spent reading this memo, and her reaction, based on the time spent, will go something like this: Less than 10 min.: Time for an employee conference and possible attitude counseling.

10-14 min.: Keep an eye on this employee; may be developing slipshod attitude.

14-15.61 min.: Employee is an efficient worker, may sometimes miss important details.

Exactly 15.62 min.: Smartass. Needs attitude counseling.

15.63-16 min.: Asswipe. Not to be trusted.

16-18 min.: Employee is a methodical worker, may sometimes get hung up on minor details.

More than 18 min.: Check the security videotape, see just what this employee was up to (e.g., possible unauthorized restroom break).

Y.T.’s mom decides to spend between fourteen and fifteen minutes reading the memo. It’s better for younger workers to spend too long, to show that they’re careful, not cocky. It’s better for older workers to go a little fast, to show good management potential. She’s pushing forty. She scans through the memo, hitting the Page Down button at reasonably regular intervals, occasionally paging back up to pretend to reread some earlier section. The computer is going to notice all this. It approves of rereading. It’s a small thing, but over a decade or so this stuff really shows up on your work-habits summary."

--Neal Stephenson, Snow Crash

Re:What McKinsey got wrong about developer productivity by rrr_oh_man on Tuesday October 24, 2023 @05:17PM (#38005754)
Thank you for introducing me to this!
Re:What McKinsey got wrong about developer productivity by ath3nd on Tuesday October 24, 2023 @01:04PM (#38002033)
In my 15 years of experience in software engineering, I've never found it either. I have, however, wasted 1000s of hours playing with poker cards and Fibonacci numbers instead of actually working. But I get paid for this, so, I guess: yay, end stage corpo capitalism!
Re:What McKinsey got wrong about developer productivity by paulcole on Tuesday October 24, 2023 @06:54PM (#38006820)
I think this is a common misinterpretation that many people fall prey to. “It’s wasting my time so it must be bad.”

Your employers aren’t optimizing for your personal productivity and happiness. They don’t mind if you waste 1000s of hours with poker cards and Fibonacci numbers if their business goals are met. This can mean making one person upset and less productive if it makes progress towards a bigger goal.

Re:What McKinsey got wrong about developer productivity by distortionfield on Tuesday October 24, 2023 @07:36PM (#38007190)
But it doesn’t make progress towards the bigger goal. That’s their whole point.
Re:What McKinsey got wrong about developer productivity by paulcole on Tuesday October 24, 2023 @09:18PM (#38007974)
All those companies failed to achieve their goals and went out of business?

Just because you don’t see the progress and don’t like the process doesn’t mean progress isn’t being made.

Re:What McKinsey got wrong about developer productivity by boxed on Wednesday October 25, 2023 @04:10AM (#38010458)
In business it's not about achieving your goals fastest, it's about not being the slowest. Just like running from a lion. This is why these businesses survive.

This is a common misunderstanding about market economies vs communism btw. In market economies there's a floor to the incompetence. In communism there is none. The ceiling isn't really different, but since there's a floor in one you will get a natural average higher in market economies. Pro-market people get this wrong all the time.

Re:What McKinsey got wrong about developer productivity by ath3nd on Wednesday October 25, 2023 @01:45PM (#38015730)
How is blindly emulating some practices that you just read about in a Scrum guide gonna contribute to the business goals of the company? The perversion of the industry is that sleazy manager/business/coaching/scrum types weasel their way into software engineering and somehow want both respect, attention, and people following what they prescribe is "THE WAY".

Imagine if the tables were turned. Developers present in all sales meetings and asking each individual sales person how much they think the call to this client is going to take in terms of story points. And how about we also go to HR and start interrogating them how many story points it takes to give somebody their office key? Busywork might be fun, but companies can do with much less, and achieve the same, or more than they do now.

After 15 years in the industry and being both an IC, a manager, and currently a VP of Engineering, I can confidently state that the best strategy one can take to achieve their business goals is to leave the software engineering to the software engineers and step the heck out of their way.

Wasting the time of people actually doing the work by arbitrary rituals you read about in a blog somewhere is not a good strategy for success. If we must go bother someone and treat them like children and force them to play cards, let's do it with another department for a change.

Re:What McKinsey got wrong about developer productivity by paulcole on Wednesday October 25, 2023 @02:40PM (#38016574)
> Imagine if the tables were turned. Developers present in all sales meetings and asking each individual sales person how much they think the call to this client is going to take in terms of story points. And how about we also go to HR and start interrogating them how many story points it takes to give somebody their office key? Busywork might be fun, but companies can do with much less, and achieve the same, or more than they do now.

I think we should do this!

> Busywork might be fun, but companies can do with much less, and achieve the same, or more than they do now.

A dangerous assumption to apply to all companies. Also the trick is deciding what "much less" looks like. Better hope you pick the right things.

I'm not saying it can't be done. It's just hard. And in some cases, you'd rather just be 10% less productive (but still productive) by following a process you hate.

Re:What McKinsey got wrong about developer productivity by rrr_oh_man on Thursday October 26, 2023 @01:23AM (#38021901)
I like you.