The Magic of Compound Efficiencies in Engineering
Plus Team Topologies, a workshop on how elite engineering teams use metrics & find out where your focus time went
As the milestone book Atomic Habits laid out, the key to life-changing habits is adopting one effectively and then layering another desirable habit on top of it.
The same is true for efficiencies in software engineering.
When your team adopts one efficiency, sees it bear fruit, then adds the next efficiency habit on top of it, the result is compounding.
In this conversation, LinearB’s CTO Yishai Beeri reveals the data on compound efficiencies as experienced by real dev teams.
“There are dev orgs that just visit their metrics dashboard every three weeks. That's nice, but that's not enough. That's not going to change behaviors that improve efficiency.”
Episode Highlights:
(2:53) Sourcing the data
(5:57) Visibility for devs & managers
(12:15) Improving code reviews
(19:30) What are compounding efficiencies?
(21:48) Streamlining the PR process
(25:52) Results from efficiencies gained
(33:40) Giving devs back more focus time
(40:45) How to get compounding efficiencies for your team
This Week’s Dev Interrupted Download Is Sponsored by gitStream
Want to cut code-review time by up to 40%?
gitStream is the free dev tool from LinearB that eliminates the No. 1 bottleneck in your team’s workflow: pull requests and code reviews. After reviewing the work of 2,000+ dev teams, LinearB’s engineers and data scientists found that pickup times and code reviews were lasting 4 to 5 days longer than they should be.
The good news? These delays can be eliminated by automating parts of the code-review process, auto-assigning the best reviewer, adding estimated review time, and more custom automations!
Learn more about how gitStream is making coding better HERE.
The Download
The Download is engineering leadership content we’re reading, watching, and attending that we think you might find valuable.
1. Lucca Rossi’s Take On Topologies
Not only is Refactoring.fm’s Lucca Rossi a friend of Dev Interrupted; he’s an avid reader. Case in point: He’s taken the time to distill his favorite takeaways from the landmark book Team Topologies by Matthew Skelton and Manuel Pais.
For more on Team Topologies, you can also listen to our podcast interview with the authors.
2. Learn How Elite Teams Set Metrics Benchmarks
The first of LinearB’s Summer Workshop Series is in the books, and Dev Interrupted’s own Dan Lines took the virtual stage to look at metrics and dashboards engineering leaders use to baseline their team’s efficiency and code quality.
Watch the workshop to find out how to baseline your team’s efficiency and code quality with team-level metrics that:
- Indicate quality and delivery risk
- Prove business value to you & your Senior/Executive leadership
- Drive OKRs that can be measured against business impact
3. Find Out Where All Your Focus Time Went
You’re not crazy; it’s harder to find time to code than it should be. Thanks to Clockwise, we finally know where all those hours are getting wasted.
Thanks for reading Dev Interrupted! If you found this post valuable, subscribe for free to get the podcast and one deep-dive engineering leadership article delivered to you every week.