Engineers make big money by building scalable long-term assets. But what does that even mean?
Your job is all about these 3 curves that make a scalable business.
You want users and revenue to grow exponentially. Bugs per day to grow linearly. Support work to grow logarithmically. Your goal is to make this happen.
That's why engineers are worth so much, we don't just do the work today, we build an asset that keeps doing the work forever. Or at least for a while.
Here's how it works:
exponential
Users and revenue come for the features and stay for the service. The more people love your service, the more friends they bring. Retention creates growth.
If you can, always work in a department that values retention. Less dopamine, more reward.
linear
Bugs scale with usage. The more users you have, the more edge cases and weird situations they'll find. Things that used to happen once a month become daily fires and frustrations. Exceptions become common.
Your code quality really begins to matter. All that annoying process stuff holding you back, chasing down 1 in 1000 edge cases? Just making sure you get to sleep at night.
https://x.com/Swizec/status/2018750989445263600
Reality, at scale, is one big pile of exceptions. That's why modeling with state machines never seems to work 😥
logarithmic
Support burden scales with bugs and exceptions. The more daily issues you have, the more folks you need dealing with those.
The job here is to build tools (and fix bugs) so the number of people running the business scales logarithmically with the number of users. Automate, reduce clicks, let robots do more.
Also true for engineering!
Use linters and static types to catch basic mistakes. Automate your deploys. Make it easy to test things. Write documentation and standard operating procedures. Remove steps from your processes.
None of this is easy or a given. Lots of startups collapse because they can't scale to match demand. Product goes to shit, people stop coming.
Building cool features is easy, keeping them running is hard.
Cheers,
~Swizec
Continue reading about The 3 curves that make a scalable business
Semantically similar articles hand-picked by GPT-4
- Why engineers are worth so much
- The future of software engineering is SRE
- When to join and leave a company, project, or trend
- How good engineering unlocks fast scaling
- The 3 budgets
Scaling Fast book free preview
Enter your email to receive a sample chapter of Scaling Fast: Software Engineering Through the Hockeystick and learn how to navigate hypergrowth without burning out your team.
Have a burning question that you think I can answer? Hit me up on twitter and I'll do my best.
Who am I and who do I help? I'm Swizec Teller and I turn coders into engineers with "Raw and honest from the heart!" writing. No bullshit. Real insights into the career and skills of a modern software engineer.
Want to become a true senior engineer? Take ownership, have autonomy, and be a force multiplier on your team. The Senior Engineer Mindset ebook can help 👉 swizec.com/senior-mindset. These are the shifts in mindset that unlocked my career.
Curious about Serverless and the modern backend? Check out Serverless Handbook, for frontend engineers 👉 ServerlessHandbook.dev
Want to Stop copy pasting D3 examples and create data visualizations of your own? Learn how to build scalable dataviz React components your whole team can understand with React for Data Visualization
Want to get my best emails on JavaScript, React, Serverless, Fullstack Web, or Indie Hacking? Check out swizec.com/collections
Did someone amazing share this letter with you? Wonderful! You can sign up for my weekly letters for software engineers on their path to greatness, here: swizec.com/blog
Want to brush up on your modern JavaScript syntax? Check out my interactive cheatsheet: es6cheatsheet.com
By the way, just in case no one has told you it yet today: I love and appreciate you for who you are ❤️