DevEx: What Drives Productivity
queue.acm.org
DevEx: What Drives Productivity
1–10 of 38 posts
Re: DevEx: What Drives Productivity
#2[deleted]
Re: DevEx: What Drives Productivity
#3> The Three Dimensions of DevEx
Our framework distills developer experience to its three core dimensions: feedback loops, cognitive load, and flow state
. These dimensions emerged from real-world application of our prior research, which identified 25 sociotechnical factors affecting DevEx.
Very solid groundwork for analyzing your development.
Re: DevEx: What Drives Productivity
#4Recent discussion: https://news.ycombinator.com/item?id=36006561
Re: DevEx: What Drives Productivity
#5> Developer experience focuses on the lived experience of developers and the points of friction they encounter in their everyday work.
I know this is captious of me, but I never understood this phrase "lived experience". As opposed to..? Is there another kind of experience?
Re: DevEx: What Drives Productivity
#6> Developer experience focuses on the lived experience of developers and the points of friction they encounter in their everyday work. I know this is captious of me, but I never understood this phrase "lived experience". As opposed to..? Is there another kind of experience?
My guess is ‘presumed’
Re: DevEx: What Drives Productivity
#7> Developer experience focuses on the lived experience of developers and the points of friction they encounter in their everyday work. I know this is captious of me, but I never understood this phrase "lived experience". As opposed to..? Is there another kind of experience?
My guess is ‘presumed’
I hear you, but it still seems redundant to me. Take the next use of the phrase:
> The developer's team, role and responsibilities, and seniority all impact their lived experience.
Why not just "all impact their experience"?
Re: DevEx: What Drives Productivity
#8The article begins with:
Engineering leaders have long sought to improve
the productivity of their developers ...
What the rest of the article fails to discuss is how upstream-processes determine developer productivity far more than the three dimensions identified. To wit, the clarity and focus of "what and why" for an effort determines the "how and when." Which makes the answer to "knowing how to measure or even define developer productivity" no longer elusive, but instead quantifiable.
Few, if any, qualified developers I have worked with have a poor DevEx when the work needed to be done is well-defined (what) and can be explained such that a solution is identifiable (why). Solutions almost always flow from these (how), with an ability to communicate the work effort possible (when).
Skip the up-front investment by stakeholders on "what and why", "how" will remain nebulous, and "when" will be just a guess.
Re: DevEx: What Drives Productivity
#9> Developer experience focuses on the lived experience of developers and the points of friction they encounter in their everyday work. I know this is captious of me, but I never understood this phrase "lived experience". As opposed to..? Is there another kind of experience?
As opposed to a statistic like lines of code written. As opposed to ‘experience’ in the prescriptive sense like ‘The developer experience here uses Docker and Webpack and therefore is modern and therefore is good’. As opposed to ‘experience’ like years-of-experience in a certain role/technology.
I’m not the author, but I found that to be a highly important distinction for them to call out. It is about the way that each individual developer feels during each individual day, in a way that is hard to capture with statistics and summaries and lists of technologies and descriptions of processes.
Re: DevEx: What Drives Productivity
#10> Developer experience focuses on the lived experience of developers and the points of friction they encounter in their everyday work. I know this is captious of me, but I never understood this phrase "lived experience". As opposed to..? Is there another kind of experience?
It's just a more complicated way of saying "personal experience"