Most people know the 4 key metrics of Dev Ops:
- Delivery lead time
- Deployment frequency
- Mean time to restore service
- Change fail rate
What would the 4 key metrics of Dev Experience be?
- Delivery lead time
- Deployment frequency
- Mean time to restore service
- Change fail rate
What would the 4 key metrics of Dev Experience be?
my picks:
🌏 Time to World Tour
Anyone can do "Hello World" with `git clone` and not teach a thing. More impt to give the developer a useful mental model of what they should know in short time.
You can't visit all 192 countries, but you can show that there are 7 continents.
🌏 Time to World Tour
Anyone can do "Hello World" with `git clone` and not teach a thing. More impt to give the developer a useful mental model of what they should know in short time.
You can't visit all 192 countries, but you can show that there are 7 continents.
🏃♀️ Time to Implement Change
Anyone can build brittle systems. But great DX optimizes for 1-2 standard deviation changes in requirements:
- find helpful docs fast (better: no docs needed)
- low edit distance
- smooth migration paths
Anyone can build brittle systems. But great DX optimizes for 1-2 standard deviation changes in requirements:
- find helpful docs fast (better: no docs needed)
- low edit distance
- smooth migration paths
https://twitter.com/swyx/status/1395172543565344770?s=20
👀 Time to Preview Change
Anyone can do a 15 min redeploy to see results of a change. Great DX reduces that 1-3 orders of magnitude:
- Fast local preview of changes (eg HMR or good tests)
- Cached rerun of results (eg @observablehq)
- Instantly deployable changes (eg @Replit)
Anyone can do a 15 min redeploy to see results of a change. Great DX reduces that 1-3 orders of magnitude:
- Fast local preview of changes (eg HMR or good tests)
- Cached rerun of results (eg @observablehq)
- Instantly deployable changes (eg @Replit)
❗ Total WTFs per Year
Anyone can design for the happy path. Great DX handles not only the good, but also the bad AND the ugly:
- Errors that don't make me think
- Billing that is predictable and boring
- Proactive warning of known issues
Anyone can design for the happy path. Great DX handles not only the good, but also the bad AND the ugly:
- Errors that don't make me think
- Billing that is predictable and boring
- Proactive warning of known issues
https://twitter.com/swyx/status/1294689838872981506
• • •
Missing some Tweet in this thread? You can try to
force a refresh
