Safe defaults. | Irrational Exuberance
Back in 2018, when I first wrote about sizing engineering teams, I was surprised how much my advice rankled a colleague. He wanted to spin up a new engineering team of two people, which I thought was a bad idea. It would be a fragile team that would fall apart quickly if it didn’t grow. It would be missing the components we’d seen make other teams successful, like an engaged manager or ability to handle on-call if someone took a vacation.
Back in 2018, when I first wrote about sizing engineering teams, I was surprised how much my advice rankled a colleague. He wanted to spin up a new engineering team of two people, which I thought was a bad idea. It would be a fragile team that would fall apart quickly if it didn’t grow. It would be missing the components we’d seen make other teams successful, like an engaged manager or ability to handle on-call if someone took a vacation. Finally, I argued that there was no real advantage to creating a new team, you could accomplish the same goals by just focusing two members of an existing…
saved by
related reading
- Writing an engineering strategy. | Irrational Exuberancelethain.com
- How and why we built our startup around small teamsnewsletter.posthog.com
- World-building IRL - by joss and Wygo - box.boxx.substack.com
- Guides | Stay SaaSystaysaasy.com
- Revised rules of engineering leadership.lethain.com
- ‘Give Away Your Legos’ and Other Commandments for Scaling Startupsreview.firstround.com
- AddyOsmani.com - 21 Lessons From 14 Years at Googleaddyosmani.com
- Gene Pool Engineering for Entrepreneurskhoslaventures.com
- Learners vs Guides: Building Your Leadership Teammollyg.substack.com
- 20 Things I've Learned in my 20 Years as a Software Engineer - Simple Threadsimplethread.com
- Learnings from Building and Scaling Ramp’s Growth Engineengineering.ramp.com
- Make an Org Chart You Want to Ship — Advice from Linear on Designing Your Teamreview.firstround.com