Friend, how good are you at your best?
Nobody cares. How good are you at your average? What about your worst?
Everyone's great at their best. When the stars align, the energy is just right, the temperature is perfect, the code hits that sweet spot between easy and challenging, you had the perfect burrito, and your beverage tastes amazing and endless.
Your fingers glide across the keyboard, your brilliance is endless, an aria sounds from the heavens when you run your code.
5 Action Steps to Senior Engineer
Get a short email series with action steps you can take right now to be true senior engineer. Go from being a pair of hands that write code to a collaborative partner that others rely on.
Here's what a reader had to say:
Hey Swiz, I really enjoyed the series. Quite useful 5-step roadmap, if everybody kept those things in mind we would be in a much better place and our industry would be a more mature and less hype-driven one. Thanks, keep up the great work!
Reality doesn't play fair
\<record scratch>
That's not how reality works you doodoo!
Reality looks like a scene from a bad sitcom.
You roll into work 10 minutes late because your car broke down, the coffee machine is broken, you spill water on your keyboard, slack pings you every 10 seconds with an oh so very important message, JIRA screams at you about bugs, production is down, your new team member can't get their local environment to run, and the PM is like "Yo, where's that feature you promised last week?"
Oh and your computer started an update in the middle of a Zoom call (you were presenting), kicked you out, and now Chrome won't start.
How good's your code now my friend?
That's where you must focus your energy. How good is your performance on a terrible annoying hell of a day?
We idolize folks like Jimmy Hendrix, Ayrton Senna, Michael Jordan, and Queen not because they had a few fantastic days here and there. We idolize them because they were great every time.
It's your typical performance that defines you. Consistency. What You Do is Who You Are as Ben Horowitz would say.
What does that have to do with flow??
Flow is when you're at your best.
Mihaly Csikszentmihalyi invented/discovered/defined flow. I wrote about it lots in Why Programmers Work at Night back when I thought flow was the only way to code.
But flow is hard to get.
Most days work is ... work. You put one foot in front of the other until you get where you're going.
That's because programming and engineering are two different things.
Programming is fun, almost art. Solving hard problems in beautiful ways. Flow is perfect.
Engineering is work. Solving hard problems in obvious stupid ways. Flow is unnecessary.
The emphasis is on how will a bunch of distracted people with no skin in the game and zero care for your code maintain this when you're not there to be brilliant?
And remember 👉 they're upset because they were late for work, spilled their coffee, and got pulled in a million directions as soon as they sat down.
If you wrote it in flow, at your most brilliant, they might not even understand your code! YOU won't understand it when you're distracted and upset.
Remember Kernighan's Law: debugging is hard.
What can you do about it?
Not much. Keep going.
When shit's going down, when everything's crap, the best way forward is through.
And when you code, write down everything. It helps you recover from interruptions.
Cheers,
~Swizec
PS: remember to read the docs
Become a *true* Senior Engineer
Get promoted, earn a bigger salary, work for top companies
Getting that senior title is easy. Just stick around. Being a true senior takes a new way of thinking. Do you have it?
Leave your email and get the 5 Action Steps to Senior Engineer - a short email course showing you steps you can take right now to become a true senior engineer and go from writing code to being a true collaborative partner that builds products.
5 Action Steps to Senior Engineer
Get a short email series with action steps you can take right now to be true senior engineer. Go from being a pair of hands that write code to a collaborative partner that others rely on.
Here's what a reader had to say:
Hey Swiz, I really enjoyed the series. Quite useful 5-step roadmap, if everybody kept those things in mind we would be in a much better place and our industry would be a more mature and less hype-driven one. Thanks, keep up the great work!
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
Want to brush up on modern JavaScript syntax? Check out my interactive cheatsheet: es6cheatsheet.com
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 ❤️