Swizec Teller - a geek with a hatswizec.com

    Meetings – a senior engineer's secret weapon

    I have a confession to make ...Β I'm starting to enjoy meetings πŸ™Š

    10 years ago I published an essay that went viral, even became the most shared article on Business Insider for a time – Why Programmers Work at Night. Later that essay turned into my first book.

    The essay says:

    1. Programmers need to think hard with lots of focus
    2. Long periods of focus are best
    3. Anything you do to disturb that focus is a total catastrophe and the worst thing ever

    And that's true when your highest impact work is banging out code. Like when building towards a tight deadline, setting up a new system, or on a small team with a clear goal.

    You know what to build, you know how, you sit down and you make magic. Bliss. 🀩

    But there comes a time in your career when writing code is no longer your highest impact contribution. You can do more. The code is holding you back.

    Yes it's fun, but how many times can you build the same old widget? Let others learn, eh.

    A 30min meeting saves 2 days of work

    This is a true story. A 30 minute meeting saved the team 2 days of work and cleared any lingering doubt in my mind. Meetings are useful.

    Swizec Teller published ServerlessHandbook.dev avatarSwizec Teller published ServerlessHandbook.dev@Swizec
    When you save 2 days of work with a 30min meeting that's the good engineering stuff πŸ”₯

    I should write about this, it's a good story

    We were in the middle of a tight sprint. Clearing large chunks of work before a looming project that's going to take weeks and determine the future of our company. No pressure πŸ˜…

    Out of nowhere the head of engineering swoops in and says: "I got this email from Twilio. Says we might start dropping SMS messages, if we don't change our integration by Oct 1st. Looks easy, let's just do it"


    Uhh we literally don't have time for this shit. This is like the worst possible project from the Eisenhower matrix. Urgent and not important.

    Eisenhower matrix
    Eisenhower matrix

    We decided we'll look into it. Team has final say on work we do or don't accept. πŸ’ͺ

    Digging through Twilio's documentation proved our worst fears. Email says "no changes necessary just enable X, Y, Z", head of eng says "looks like a quick afternoon", documentation says "You have to change how you talk to our API and we handle the rest"

    To make it worse: part of our integration lives in a system none of us have access to. Don't know how it works, didn't even know it existed until we broke it recently by removing a useless function call. Chesterton's fence style.


    Do we even need to do this?

    This wasn't my first rodeo with SaaS providers dear reader. That email, it smelled like a sales pitch.

    You add new phone numbers to finally separate dev, staging, and production and 3 days later there's an email saying you have to enable some fancy new integration for large volume πŸ€”. Even the docs keep talking about "messages per second".

    We're at the "messages per minute" stage ...

    Okay before we go down this road, let's talk to our Twilio account rep and ask why they think we need this.

    The PM goes "Sure Swiz but I have no idea what you're talking about, can you join?"

    Heck yes I can join!

    Guess what – they saw that we started buying more numbers, figured we're scaling our SMS marketing, and wanted to offer a better service aimed at high volume senders. A-ha!

    We explained that no, we bought more numbers to stop sending development messages from production. And we prefer to send every message from the same phone number. We only need 1.

    "Well in that case, you don't need any of this"

    And that's how a 30min chat saved us 2 days of work. Way better ROI than 30min of coding.


    PS: When you code, write down everything. Helps you recover from distraction.

    Did you enjoy this article?

    Published on October 1st, 2021 in Mindset, Learning, SeniorMindset

    Want to become a true senior engineer?

    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 Senior Mindset series - a series of curated essays on the mindset of a senior software engineer. What it takes to get there, what should you do when you're there, how to change the way you think.

    The Senior Mindset series

    Get a series of curated essays on the mindset of a senior software engineer. What it takes to get there, what should you do when you're there, how to change the way you think.

    it describes my days in a way I have not read before.

    This was a very enlightening article about being a senior engineer.

    Join over 14,000 engineers just like you already improving their careers with my letters, workshops, courses, and talks. ✌️

    Have a burning question that you think I can answer?Β I don't have all of the answers, but I have some! Hit me up on twitter or book a 30min ama for in-depth help.

    Ready to Stop copy pasting D3 examples and create data visualizations of your own? Β Learn how to build scalable dataviz components your whole team can understand with React for Data Visualization

    Curious about Serverless and the modern backend? Check out Serverless Handbook, modern backend for the frontend engineer.

    Ready to learn how it all fits together and build a modern webapp from scratch? Learn how to launch a webapp and make your first πŸ’° on the side with ServerlessReact.Dev

    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 ❀️

    Created bySwizecwith ❀️