Every layer of review makes you 10x slower - apenwarr
apenwarr.ca · 2,807 words · saved by 1 readers
We’ve all heard of those network effect laws: the value of a network goes up with the square of the number of members. Or the cost of commun...
Every layer of review makes you 10x slower We’ve all heard of those network effect laws: the value of a network goes up with the square of the number of members. Or the cost of communication goes up with the square of the number of members, or maybe it was n log n, or something like that, depending how you arrange the members. Anyway doubling a team doesn't double its speed; there’s coordination overhead. Exactly how much overhead depends on how badly you botch the org design. But there’s one rule of thumb that someone showed me decades ago, that has stuck with me ever since, because of…
saved by
related reading
- Shipping Code Faster - by Ryan Peterman - The Peterman Postdeveloping.dev
- There's no reason for software to be slow anymoredanluu.com
- Some reasons to work on productivity and velocitydanluu.com
- Everything I know about good system designseangoedecke.com
- Cognitive load is what mattersminds.md
- AI is removing the middle class of software engineeringblog.florianherrengt.com
- How To Do Lessalexturek.com
- Thoughts on slowing the fuck downmariozechner.at
- Revised rules of engineering leadership.lethain.com
- Notes on software qualityanthonyhobday.com
- AddyOsmani.com - 21 Lessons From 14 Years at Googleaddyosmani.com
- Why Over-Engineering Happens | Yusuf Aytasyusufaytas.com