The Ultimate DevEx Playbook: A Step-by-Step Guide to Improving Developer Experience
tl;dr: Data on metrics like revenue, employee turnover, and job satisfaction provide crucial insights into efficiency, quality, and direction. But they don’t capture if your engineers are feeling overworked, underappreciated, or unmotivated. Access the Ultimate DevEx Playbook for insights and best practices from Jellyfish and AWS so you can get closer to a better developer experience now.featured in #567
Improve Developer Experience With A Combination Of Surveys And System Metrics
- Miikka Holkeri tl;dr: The most challenging thing about running developer experience surveys is knowing what questions to ask. That’s why Swarmia teamed up with psychometrics experts to develop a 32-question survey framework that covers all aspects of software development, from architecture to cross-team collaboration. You can copy the questions here to run your own survey.featured in #527
Stripe's Monorepo Developer Environment
- Nelson Elhage tl;dr: “I worked at Stripe for about seven years, from 2012 to 2019. Over that time, I used and contributed to many generations of Stripe’s developer environment – the tools that engineers used daily to write and test code. I think Stripe did a pretty good job designing and building that developer experience, and since leaving, I’ve found myself repeatedly describing features of that environment to friends and colleagues.”featured in #517
The New Developer Nation Survey Is Live! Join Forces With Thousands Of Devs Worldwide!
tl;dr: Take part in the Developer Nation Survey and influence the future of the developer ecosystem. Every respondent will get a virtual goodie bag packed with FREE resources and the chance to win amazing prizes! [Start now!](https://developereconomics.net/?member_id=pointer)featured in #473
How To Arrange GitHub Actions To Improve Feedback Cycles
- Aritra Mondal Joerg Fiedler tl;dr: "Our key takeaways include reorganizing the GitHub workflow to separate concerns, reusing test containers, and sharding tests for parallel execution. These actions resulted in a significant reduction in test execution time and faster feedback cycles."featured in #472
The Ultimate Guide To Developer Experience
- Ari-Pekka Koponen tl;dr: Investing in developer experience is a bit of a no-brainer if you want to improve developer retention and productivity. But what are some practical ways to drive great DX in your organization?featured in #431
DevEx Principles: Minimize Switching Contexts
- Kathy Korevec tl;dr: Over the past 15 years shipping products for Heroku, GitHub, and now Vercel, I've learned a lot about what developers need to succeed: (1) Minimize switching contexts. (2) Remember, you are a chef cooking for chefs: Respect the craft. (3) Automate anything that can be automated. (4) Optimize for time to code. (5) Be mindful of breaking changes. People’s services depend on your services. (6) Don’t bury the lede.featured in #389
featured in #376
How We Improved The Development Experience For Our Client Developers
- Anna Granhed Nandini Singh tl;dr: We wanted to improve the coding experience for our development teams through infrastructure changes. We conducted research among 318 engineers and learned that: (1) Developer productivity and satisfaction were compromised due to longer build times, as per our Engineering Satisfaction survey results. (2) Build times on Apple silicon machines were 43% faster than Intel-based Mac systems, overall, and up to 50% faster for Android builds and 40% faster for iOS builds. And more.featured in #365
featured in #350