/DevEx

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

Shipping Spotify’s Culture: 5 Plugins (And 4 Principles) For Supercharging Developer Experience At Scale

- Tyson Singer tl;dr: 4 principles are DevEx at scale: (1) Keep squads fast by keeping them small, capable, and aligned. (2) Make engineering excellence and quality an everyday practice. (3) The best solutions come from the bottom up, so empower the teams doing the work. (4) Our fellow developers are our customers, so build with empathy.

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

The End Of Localhost

- Shawn Wang tl;dr: "Dev environments should be cattle, not pets. It looks likely that most development will not be done on localhost in future." Shawn highlights that one of the biggest obstacles of developing is the local environment, highlighting how big tech companies are investing to move away from this and new technologies, such as edge computing, could be a way to solve for this problem.

featured in #350

Developer Experience Infrastructure (DXI)

- Kenneth Auchenberg tl;dr: Kenneth defines DX as "the holistic experience offered to developers throughout the lifecycle they interact with your product or service" and lists the "table stakes" experience for developers in 2022, such as having documentation and content, great attention to detail on error messages, API references, baseline API infrastructure, debugging tools, and more. He discussed the cost of poor DX and the transition from DX to DXI as an emerging trend.

featured in #348

Remote Development At Slack

- Sylvestor George tl;dr: In this article, “remote development environments” refer to AWS EC2 instances where engineers make code changes and can see a running Slack application with those changes.

featured in #335

Development Environments

- Dimitri Sabadie tl;dr: "I want to use this blog article to ask questions and not necessarily answer them, but discuss them: “how we should be developing in the modern era?” Dimitri starts with the following problems: (1) TUIs are not graphically rich enough. (2) CLI-based composition is a "nightmare of running the same command over and over." (3) A terminal is just static text and nothing changes unless you run a command.

featured in #330