Jump to content

User:Geekjock1/sandbox

From Wikipedia, the free encyclopedia

Developer experience (DX) encompasses how developers feel about, think about, and value their work.[1] DX pays particular attention to software development environments and the particular points of friction developers encounter in their everyday work across workflows, processes, and practices.[2]

Definitions

[edit]

"Developer experience" is a concept that began to emerge in 2012, inspired by the expansion of user experience (UX) to encompass the end-to-end experience of a product.[3] The term "developer" refers to anyone who engages in the activity of developing software, while "experience" describes participation in that process, not simply having experience.[4]

An early definition of DX, published by Fabian Fagerholm and Jürgen Münch, outlined three dimensions: cognitive, affective, and conative, which correspond to the trilogy of mind theory from social psychology (see also: psychology of self).[5][6] These three factors respectively describe DX as encompassing how developers intellectually perceive their development infrastructure, how they feel about their work, and how they see the value of their contributions.[7]

In 2021, a comprehensive approach to improving developer experience was published by researchers Abi Noda, Margaret-Anne Storey, and Michaela Greiler. The paper identified more than 25 socio-technical factors that affect the developer experience. These factors include interruptions, unrealistic deadlines, well-organized code, and pain-free releases.[8]

Measurement

[edit]

A later developer experience framework published in ACM Queue by Noda, Storey, and Greiler, and Nicole Forsgren, author of Accelerate, condensed the 25 factors identified in their earlier work into three dimensions affecting developer experience: feedback loops, cognitive load, and flow state.

This updated framework has identified several areas that can be measured to assess their impact on developer experience, highlighting that developer experience cannot be reduced to a single metric. The framework therefore emphasizes the significance of capturing comprehensive measurements that cut across developers' “perceptions and workflows."

Industry trends, initiatives, and teams

[edit]

Major business consulting and market research firms have identified developer experience as a notable technology trend. According to a 2022 survey conducted by Forrester Research, 75% of enterprise leaders rated DevEx as "important/very important to business strategy execution."[9]

Developer experience has also gained increasing attention as a crucial factor in software development at leading technology companies, with engineering leaders and C-level executives at industry giants such as Amazon, Google, Microsoft, and Spotify recognizing its increasing importance in recent years.[10][11][12][13]

Dedicated DevEx teams leading initiatives to improve developer experience are often part of the broader trend of platform engineering. Gartner research estimates that that 80% of software engineering organizations will have established platform teams by 2026.[14] The charters of internal developer experience teams at technology leaders like Google, Stripe, and Twitter commonly prioritize ease and enablement as key objectives.

Industry discussions: significance  

[edit]

Recent industry reports have also highlighted the significance of enhancing developer experience for businesses.[15]

McKinsey's research indicates that developer experience can help engineering organizations enhance productivity, business performance, and talent retention.[16] A study conducted by McKinsey in 2020 revealed that companies with superior developer work environments achieved revenue growth four to five times higher than their competitors.[17] The 2021 State of DevOps report also demonstrated that high-performing engineering organizations were twice as likely to surpass organizational performance objectives as low performers, outperforming competitors in metrics such as profitability, market share, and customer satisfaction.[18]

Internal and external developer experience

[edit]

This article primarily addresses internal developer experience, which refers to the quality of the experience that software developers have within an organization. However, it is important to note that developer experience is also a significant consideration for businesses that primarily offer software as a service (SaaS) products whose end-users are developers.

See also

[edit]

Developer (software)

Software development process

Developer relations

Platform evangelism

User experience

Customer experience

Employee experience management

References

[edit]
  1. ^ Greiler, Michaela; Storey, Margaret-Anne; Noda, Abi (2022). "An Actionable Framework for Understanding and Improving Developer Experience". IEEE Transactions on Software Engineering: 1–1. doi:10.1109/TSE.2022.3175660. ISSN 1939-3520.
  2. ^ Greiler, Michaela; Storey, Margaret-Anne; Noda, Abi (2022). "An Actionable Framework for Understanding and Improving Developer Experience". IEEE Transactions on Software Engineering: 1–1. doi:10.1109/TSE.2022.3175660. ISSN 1939-3520.
  3. ^ Fagerholm, Fabian; Münch, Jürgen (2012-06). "Developer experience: Concept and definition". 2012 International Conference on Software and System Process (ICSSP): 73–77. doi:10.1109/ICSSP.2012.6225984. {{cite journal}}: Check date values in: |date= (help)
  4. ^ Fagerholm, Fabian; Münch, Jürgen (2012-06). "Developer experience: Concept and definition". 2012 International Conference on Software and System Process (ICSSP): 73–77. doi:10.1109/ICSSP.2012.6225984. {{cite journal}}: Check date values in: |date= (help)
  5. ^ Fagerholm, Fabian; Münch, Jürgen (2012-06). "Developer experience: Concept and definition". 2012 International Conference on Software and System Process (ICSSP): 73–77. doi:10.1109/ICSSP.2012.6225984. {{cite journal}}: Check date values in: |date= (help)
  6. ^ "Conation: An important factor of mind". www.edpsycinteractive.org. Retrieved 2023-03-29.
  7. ^ Fagerholm, Fabian; Münch, Jürgen (2012-06). "Developer experience: Concept and definition". 2012 International Conference on Software and System Process (ICSSP): 73–77. doi:10.1109/ICSSP.2012.6225984. {{cite journal}}: Check date values in: |date= (help)
  8. ^ Greiler, Michaela; Storey, Margaret-Anne; Noda, Abi (2022). "An Actionable Framework for Understanding and Improving Developer Experience". IEEE Transactions on Software Engineering: 1–1. doi:10.1109/TSE.2022.3175660. ISSN 1939-3520.
  9. ^ "Forrester: Elevating The Developer Experience - Investments In Tools And Automation Leads To Higher Productivity, Profitability, And Developer Satisfaction" (PDF).
  10. ^ Kim, Eugene. "Amazon CEO Andy Jassy is trying to fix a crumbling engineering culture with a new unit that tackles 'foundational pain points' raised by the company's frustrated developers". Business Insider. Retrieved 2023-03-29.
  11. ^ Popper, Ben (2023-02-03). "Why developer experience is the key to better software, straight from the OCTO's mouth (Ep. 534)". Stack Overflow Blog. Retrieved 2023-03-30.
  12. ^ "07-19-22 Inspire Keynote Satya Nadella" (PDF).
  13. ^ "Spotify Backstage | How Backstage made our developers more effective — and how it can help yours, too". backstage.spotify.com. 2021-09-23. Retrieved 2023-03-29.
  14. ^ "Gartner Identifies the Top 10 Strategic Technology Trends for 2023". Gartner. Retrieved 2023-03-29.
  15. ^ www.gartner.com https://www.gartner.com/doc/reprints?id=1-291VYN5L&ct=220207&st=sb;ct=220207&st=sb. Retrieved 2023-03-29. {{cite web}}: Missing or empty |title= (help)
  16. ^ "Why your IT organization should prioritize developer experience | McKinsey & Company". www.mckinsey.com. Retrieved 2023-03-29.
  17. ^ "How software developers can drive business growth | McKinsey". www.mckinsey.com. Retrieved 2023-03-29.
  18. ^ "State of DevOps 2021" (PDF).
Retrieved from "https://en.wikipedia.org/w/index.php?title=User:Geekjock1/sandbox&oldid=1147386505"