Disproportionately impactful engineering teams are distinguished by effectively shipping the right work. System optimization is part of that remit, but only part of it. The larger aspect is shipping the right work, and that’s an aspect where your CEO is actually well-positioned to help you. If your CEO is in the trenches working with you on reducing your build times, then you’re in a lot of trouble (either they aren’t doing their job or they are doing their job and they think you are not doing yours). You should be optimizing the engineering organization’s operations, and should rarely need to surface those details upwards unless you want to occasionally brag (yay, we’re good at this), are asked to provide deeper context, or need to justify an investment.
What does it mean to be a cost center?
from Irrational Exuberance
- Original layout !(https://www.joelsimon.net/imgs/evo_plans/resul...from joelsimon.net
- Deep and shallow modules: The best modules are deep: they allow a ...from John Ousterhout
- More things than you would think are dynamic strategic problems. If...from marcelo.rinesi
- 1. The code that gets written is the code that’s easier to write. 2...from Fernando Borretti
- Amdahl's law is often used in [parallel computing](https://en.w...from en.wikipedia.org
- **THE PRIORITIZATION MATRIX** All of the projects and activities o...from review.firstround.com
- In machine learning, double descent is a surprising phenomenon wher...from chris-said.io
- One of my favorite systems papers ever is the [COST](https://www.us...from blog.nelhage.com