hockeystick moments are the biggest opportunity of your career. It's exciting and kinda scary. Everything changes!
I wrote Scaling Fast: Software Engineering Through the Hockeystick as your guide. 16 years of startup experience condensed into 240 pages
https://t.co/juu00EGenC
Scaling Fast is based on startup war stories, academic research papers, talking to my mentors, and reading industry insights. It shows you what it takes to survive and thrive through the hockeystick. You'll learn about scaling teams and scaling code, how they influence each other, and why none of it matters if the business is bad.
Scaling Fast: Software Engineering Through the Hockeystick is organized in 3 sections:
- Scaling the Business
- Scaling the Team
- Scaling the Tech
The business part, that's to help you evaluate the companies you join, this isn't a business book.
The team part, that's key to shaping your everyday. We talk about delegating decisions, empowering engineers, working smooth instead of fast, finishing things all the way to done, good code review culture, and shipping incrementally without risky big bang releases.
The tech part, that's my favorite. We talk about good abstractions, architectural complexity, observing your systems break, making steady improvements to your code without huge refactoring sprints, why tests don't solve everything, what's even worth testing, how your team structure impacts what you can do with the code, and why solving today's problem is more important than building for an imagined future.
None of it is about numerical scaling [name|]. That's easy in 2025. Computers are fast. The challenge is building complex systems that don't fit in any one person's brain without breaking the business.
oftware engineering when your whole company changes every 6 months is the fun part of this gig. And that's what Scaling Fast is about.
👉 https://t.co/juu00EGenC
@DennisCode@dsp_ Right now wracking my brain with multi-tenant MCP. Making it so multiple end-users can share the same service-level MCP auth without leaking data
Would be cool to have more native support for this. Feels very optimized for personal use-cases
Being a founder is weird because you’re good at a lot of things and can probably easily get a job in Product, Marketing, Engineering, Sales/GTM, VC, etc. but the combination mixed with your god-given temperament means you are unemployable and must build your own thing
3 months ago I suggested auto-fixing PRs and there were pitchforks
This week I shipped and barely anyone noticed. Fixed 79 pull requests since Tuesday. Just works quietly in the background
funny how fast attitudes change
perhaps no meetings and quiet slack is a sign that I too should fire up the new game
eh no that's an evening activity it's nice to finally get through my PR queue
My “is engineering a valuable pursuit” math.
An outcome-oriented, creative engineer is now a 1000x engineer.
A tabs-vs-spaces-debating, miss-forest-for-trees engineer is now a -10x engineer.
The regular knowledge worker is now a 2x engineer.
This is also backed by the distribution of token consumption we see in both our startups and enterprise base. Engineers and software factories will consume exponentially more tokens.
If there’s a takeaway from Anthropic’s success, it’s that coding is the #1 killer app of AI.
Late night thought: Software consulting is dead.
You used to hire expensive consultants to tell your cheaper army of engineers what to do.
But now every engineer commands an army of cheap coders so you simply lay off the ones who can’t fill the consultants’ shoes.
@GergelyOrosz Yep! This thought spurred by talking to consultant friends all going into “We build you a software factory”
and then those of us former consultants agreeing that this should be in-house because it’s idiosyncratic and needs to adapt to team behavior quickly