Live data from Hacker News

DevEx: What Drives Productivity

queue.acm.org

31–38 of 38 posts

Re: DevEx: What Drives Productivity

#31

Has the research behind DORA and SPACE been replicated? I'm very suspicious of survey grounded research. p-values in the social sciences are high for a reason.

No doubt it will come out in a few years as total quackery.

All these books/frameworks are all the same.

Accelerate: "Copy what successful teams do and your team will suddenly be successful"

The Phoenix Project: "IT department was bad, they made small changes and then eventually they all lived happily ever after"

Re: DevEx: What Drives Productivity

#32
post #14

I posted this comment in response to the previous submission [1] of this same "paper": Also note that the prior work they repeatedly cite (no less than 5 times in as many paragraphs, and indirectly referenced several times in relation to the 20+ "sociotechnical factors"), i.e. reference number (9), is based on "semi-structured interviews with 21 developers". While a lot of the observations and recommendations are cor…

This by the same team who brought you the DORA metrics and the SPACE framework. I suspect it is really a vehicle to sell books and consulting, despite the article largely making sense. Maybe it is atonement of some sort.

Thanks for pointing that out. Although I do think DORA metrics make some sense, it seems like an unnecessary framework considering what the folks in queueing theory have done over the years.

Anyone claiming we need to invent our own metrics needs to read Reinertsen.

Re: DevEx: What Drives Productivity

#33
post #14

I posted this comment in response to the previous submission [1] of this same "paper": Also note that the prior work they repeatedly cite (no less than 5 times in as many paragraphs, and indirectly referenced several times in relation to the 20+ "sociotechnical factors"), i.e. reference number (9), is based on "semi-structured interviews with 21 developers". While a lot of the observations and recommendations are cor…

Well, yes, taking established findings and twisting them into a memorable or easily usable shape is what one does when trying to popularise concepts. (E.g. how the Shewhart/Deming cycle is related to the scientific method, or how the cost/speed/quality triangle restates "everything is a trade-off".)

That says very little substantive about their results, though, so I'm curious how you think that matters to the discussion of developer productivity!

Re: DevEx: What Drives Productivity

#34

Earlier quoted context omitted.

This by the same team who brought you the DORA metrics and the SPACE framework. I suspect it is really a vehicle to sell books and consulting, despite the article largely making sense. Maybe it is atonement of some sort.

Thanks for pointing that out. Although I do think DORA metrics make some sense, it seems like an unnecessary framework considering what the folks in queueing theory have done over the years. Anyone claiming we need to invent our own metrics needs to read Reinertsen.

I'm sure you have seen it already, but there has been some sound criticism of the DORA metrics: https://isthisit.nz/posts/2022/state-of-the-dora-devops-metr...

Though I disagree with Logan about the change failure rate (see https://two-wrongs.com/you-can-reliably-measure-change-failu...), I still think he is spot on in terms of MTTR.

Strongly seconding Reinertsen for anyone interested in this, though. I think this article of yours is particularly insightful and of high quality: https://lucasfcosta.com/2022/08/31/engineering-metrics.html

Re: DevEx: What Drives Productivity

#35
post #14

I posted this comment in response to the previous submission [1] of this same "paper": Also note that the prior work they repeatedly cite (no less than 5 times in as many paragraphs, and indirectly referenced several times in relation to the 20+ "sociotechnical factors"), i.e. reference number (9), is based on "semi-structured interviews with 21 developers". While a lot of the observations and recommendations are cor…

> Although DevEx is complex and nuanced, teams and organizations can take steps toward improvement by focusing on these three key areas.

I feel like they are aware that not everything fits into the framework perfectly, but if your organization was trying to improve DevEx, this framework is a place to start.

Re: DevEx: What Drives Productivity

#36
for everyone there is a salary / guarantee of future income point where they can just "get on with it" - go hell for leather at work and be happy their family's future is secure anyway.

Welfare states reduce that level, this subsidising businesses (!) but at some point you gotta pay if you want more than the basics. It's not extrinsic motivation - it's much more a hygiene factor to allow intrinsic motivation to come tomplay

Re: DevEx: What Drives Productivity

#37

lol @ ebay and DevEx. (one of the examples in the article) When I was there (up to 2017) the team that made the internal web framework, Raptor, refused to let anyone see the source code. I mean people that worked at the company, they wouldn't let people sitting 15 feet from them see the source code to the web framework that they used all day to work. Of course you could easily see it in any Java IDE, but they didn't…

> They can't even get the color scheme aligned. Again, if they said 'nobody cares' that's just prioritization, but I know that this has been attempted at least 5 times with teams of a dozen people spending up to a year on it. Not being able to get color scheme misalignment fixed with multiple team-years’ of effort is shocking and appalling.

If you were on the web in the late 90s you remember a time when the default web page background was grey. The background on some pages on myebay section of ebay.com are still grey (some of them) for that reason!

Re: DevEx: What Drives Productivity

#38

Has the research behind DORA and SPACE been replicated? I'm very suspicious of survey grounded research. p-values in the social sciences are high for a reason.

The DevEx dimensions of Feedback Loops, Cognitive Load, and Flow State can be measured without surveys. An example here: https://docs.kedehub.io/kede-manage/kede-devex.html
Post reply on HN