DX Digest: Sept 11, 2023
Next off-the-record discussion, Sept 28 11am PT, 2pm ET.
Welcome to this week’s digest. We hope you had a chance to check out our upcoming “off-the-record” discussion led by Lauren Darcey and Eric Kuck from the Reddit Android Platform team. We have a few spots remaining, if you would like to sign up here is the link to the registration page.
For this week we have a round up of “counter-productive” developer measures.
In favor of the worst programmer
If your team is still measuring productivity using lines of code written, or story points completed, you would be doing a disservice to the engineers on your team who are enabling others to do great work!
The ultimate guide to developer counter-productivity
Everyone knows measuring developer productivity is hard.
In this article, John anecdotally measures how much developer time is sunk doing non-constructive activities. Although this isn’t a silver bullet, we have noticed a few companies doing developer surveys to measure such toil at scale.
Increasing adoption rate with internal development platform at Spotify
A quick journey of Backstage evolution at Spotify, and how being open source and encouraging everyone to contribute helped Spotify increase the internal platform adoption rate. “If they build it, they will use it.”
Interestingly, other organizations using Backstage get “stuck trying to get past the 10% adoption rate.”
The real story of how yarn 3 became yarn 2
Versioning is not an easy task. SemVer and CalVer certainly help developers keep track of open source projects, but sometimes this can be goofed up if the terminology is not consciously standardized.