Revised rules of engineering leadership. | Irrational Exuberance
From early 2014 through late 2020, I was working in hypergrowth environments, which are challenging, but also educational. The most valuable feature of hypergrowth is that your mistakes reveal themselves next month rather than next year, because things go wrong very loudly when you’re moving fast. I’ve been thinking a lot about hypergrowth recently, because Imprint’s business is growing quickly and we did a large batch of hiring last year, but also because the AI-tooling shift has changed the pace at which it’s possible to work.
From early 2014 through late 2020, I was working in hypergrowth environments, which are challenging, but also educational. The most valuable feature of hypergrowth is that your mistakes reveal themselves next month rather than next year, because things go wrong very loudly when you’re moving fast. I’ve been thinking a lot about hypergrowth recently, because Imprint’s business is growing quickly and we did a large batch of hiring last year, but also because the AI-tooling shift has changed the pace at which it’s possible to work. This post documents the new rules I’ve revised my approach to…
saved by
related reading
- Roadmap decisions rather than dates.lethain.com
- AI is removing the middle class of software engineeringblog.florianherrengt.com
- Impact, agency, and taste | benkuhn.netbenkuhn.net
- Every layer of review makes you 10x slowerapenwarr.ca
- How I ship projects at big tech companiesseangoedecke.com
- AddyOsmani.com - 21 Lessons From 14 Years at Googleaddyosmani.com
- Growing as an engineer in a world of AInlopes.dev
- Writing an engineering strategy. | Irrational Exuberancelethain.com
- How To Do Lessalexturek.com
- Leading Effective Engineering Teams in the Age of GenAIaddyo.substack.com
- Mistakes I see engineers making in their code reviewsseangoedecke.com
- Principles for building a design engineering practicekarlkoch.me