Swizec Teller - a geek with a hatswizec.com

Senior Mindset Book

Get promoted, earn a bigger salary, work for top companies

Senior Engineer Mindset cover
Learn more

    Why you should write [code] every day

    Yesterday, Corey asked me about the best advice I have to give.

    It was for a podcast episode of The Write Stuff, his podcast about writing. Going to be a great episode. Gonna share when it's out 🎧

    But his question kept me up at night. It totally wasn't battling Gatsby and mdx. Nu-uh, not me.

    What is the best advice you can give to an aspiring writer, programmer, engineer, artist, entrepreneur, practitioner like you? A doer. Creator.

    And I believe it's this 👇

    1. Your taste is better than your skill
    2. Practice every day

    Your taste is better than your skill

    Ira Glass speaks of The Gap. That place between taste and skill where growth happens.

    You see, you get into this game because you have good taste. You read good writing, and you like it. You use delightful software, and you love it. You see a beautiful website, and you think it's great. You see art, and you think, "Wow."

    That's your taste. That's what you're trying to achieve.

    And you write some stuff, build some code, make a website, draw some art. And you think it's shit.

    Your code doesn't work, your writing doesn't flow, your website looks like crap, and your art is kinda wonky.

    That's okay! That's your taste leaping ahead of your skill.

    To bridge the gap, you need a volume of work. And you need feedback. Feedback from yourself, from your peers, from everyone who will give it.

    Volume of work is the only way. Make a thing. Fix the thing. Improve your skill until it matches your taste. Soon enough you'll love the stuff you make.

    And with practice your taste will improve as well. You might never catch up and that's great!

    Practice every day

    Quickest way to get that volume of work? Practice!

    If you practice once a year, I don't think that counts. You'll build some skill, but between sessions, you'll forget everything you learn. Plus, in the 60 adult years you've got, you'd make only 60 attempts.

    60 is not enough.

    If you practice once a month, that's better. 12 attempts per year, 180 in your adult life. Great for skills you aren't that interested in or that take several days to complete. Like hiking. Or car repairs. Maybe launching tiny apps?

    A few hours of practice every month could do wonders. Each session is intense, so you learn a lot. And a month is short enough that you remember what you've learned and can build on it.

    But it's often hard to clear an entire day for stuff.

    That's where weekly practice shines. 3120 attempts in your adult life.

    Two orders of magnitude more practice than monthly practice. Calendars are weird like that.

    Just 1 hour of practice per week. Like sitting down for an hour every Monday morning to write a newsletter to 10,000 people. Or going for a run. Or writing some code with that new stuff you're learning.

    That's 3120 hours of practice in your adult life. A monthly practitioner would have to spend 5 hours each session to beat you. 5 hours is one hell of a commitment compared to just 1 hour 🧐

    And what's more: Weekly practice compounds more than monthly practice.

    Because you remember more from last time, because you're more in the groove, it's easier to get started, easier to keep going, and you build skills on top of each other faster.

    Which is where daily practice trumps all.

    Even skipping weekends you get 15,120 hours of practice in your adult life. With just an hour a day.

    That's crazy town. What would take a lifetime with weekly practice takes just 12 years when you practice daily.

    Yes, 12 years sounds like a lot. But compared to 60?

    Practicing every day compounds like crazy as well. Each day is fresh in your mind when you start the next. You know what went wrong, you feel what went right. You know exactly what to do next.

    You can even work on the same project over many days solving different parts of it because it's fresh in your mind.

    But how do you practice every day?

    The best way is a job doing the thing you want to practice.

    Jobs are great at feeding you realistic new challenges to solve every day. Jobs are great at forcing you to practice every day. Jobs are great at crushing your fear of the empty page and forcing you to sit down and get it done.

    The hardest part of any creative endeavor is starting. That moment when you sit down and nothing happens for 5 minutes and you want to run away and hide in social media or Netflix or take a nap.

    A job won't let you do that. Gotta sit there and do the thing.

    Once you've done the thing. A new challenge appears.

    It's great 👌

    When you can't or don't want to get a job doing the thing, your best bet is to challenge yourself. Or to find a challenge group.

    Published on December 3rd, 2018 in Learning, Personal, Writing

    Did you enjoy this article?

    Continue reading about Why you should write [code] every day

    Semantically similar articles hand-picked by GPT-4

    Senior Mindset Book

    Get promoted, earn a bigger salary, work for top companies

    Learn more

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

    Created by Swizec with ❤️