3 ms·
"Today, many organizations aiming to improve developer productivity are finding that a new developer-centric approach focused on developer experience (also know
by Animats 4y ago
"Today, many organizations aiming to improve developer productivity are finding that a new developer-centric approach focused on developer experience (also known as DevEx) unlocks valuable insights and opportunities."
That reads like the beginning of a pitch on r/Metaverse_Blockchain.
One of the references, "What Happens When Software Developers are (un)Happy"[1] is more useful.
[1] https://www.sciencedirect.com/science/article/pii/S0164121218300323?via%3Dihub https://www.sciencedirect.com/science/article/pii/S016412121...
- hliyan 4y agoAlso 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 correct (and are obvious to any seasoned engineering manager), this seems like an academic exercise in picking three somewhat disparate aspects of development and trying to fit them into a geometric shape (an equilateral triangle) and then calling it a framework.
- ororroro 4y agoPersonally I am shocked that a company (DX) that sells developer survey tools would recommend surveying developers.
- dimitarbak 3y agoThey present a framework. Measuring the three dimensions of Feedback Loops, Cognitive Load, and Flow State can be done without surveys. Example here: https://docs.kedehub.io/kede-manage/kede-devex.html https://docs.kedehub.io/kede-manage/kede-devex.html
- spartanatreyu 3y agoTo their credit, they mention that customers should be running fewer survey's with more thought put into making it a higher quality survey then actually following through with the results rather than spitting out more lower quality surveys.
- musicale 3y agoThe ACM Queue article didn't clearly explain what they meant by productivity or how they evaluated it. [1] appears to do better by classifying self-reported outcomes into positive and negative categories. Classifying comments into the high or low productivity category seems challenging, but at least they provided a few examples. More importantly they identified a range of other positive and negative outcome categories.