When's the last time you tried something new?
I don't mean a new library or programming language or a new video game. No, something completely new. A skill you've never tried before that maybe you wouldn't even think to try unless somebody else gets the idea for you.
It can be a lot of fun! And useful.
Last week my partner surprised me with an intro to pottery class. I sucked and that was the best part.
Before Friday I'd never seen a pottery wheel in person. They're devilish little things. You step on the pedal and it spins.
You try the pedal a few times and think "Oh yeah I got this, supes easy to control". Then you put the clay on and suddenly there's bits and pieces flying everywhere. Clay in your hair, clay on the floor, on your glasses, everywhere! Suddenly your twinkle toe foot feels like a blunt instrument with no control of the throttle.
Great fun.
Then the water comes out and you put your hands on the clay. Gently at first then with more force. It doesn't matter. Your pot doesn't look like a pot at all.
And it doesn't matter. You're not trying to become the next great pottery master. You're just exploring the clay.
What happens if I turn my hand like this? What if I put my face right next to the clay? Oh suddenly I have more control but now I can't see because the dirty water gets all over my glasses. What about if I press here with my finger? What if my elbow lifts from my lap? What about using the outside hand to shape the pot? No that doesn't work for tall bowls. What if I press inside and pull out? Oh now it's a plate but there's a little spyre in the middle. Oh I can press that down with the sponge. Great now my hand wobbled and the whole thing fell off.
Before you know it, 2 hours have passed and your 8th piece looks like a fucking masterpiece next to the mangled pile of clay from your 0th attempt.
Pottery is a tacit skill, you learn by doing. No amount of reading or studying will help you make a better pot. Only piles of tortured clay will get you there.
It's the same with programming.
Wanna write better code? Write lots of code. Want to design better systems? Design lots of systems. Want to get better at interviewing? Go to lots of interviews. Want to get better at leading technical discussions? Lead lots of technical discussions. Want to get better at solving bugs? Solve lots of bugs. Want to improve your architecture? Architect lots of code. Want better domain modeling? Model lots of domains.
Pottery and programming are kind learning environments. You do a thing, get instant feedback, and improve. When you're in a kind learning environment, doing the thing for a while is the best way to improve. Experience makes you better.
Wicked learning environments, where feedback is delayed or obscured, are tougher. We'll talk about that some other time :)
Cheers,
~Swizec
Continue reading about When's the last time you tried something new?
Semantically similar articles hand-picked by GPT-4
- Quick tip for system design interviews
- Why you should write [code] every day
- Sucking is the first step
- How *do* you standout as a developer?
- Software dev isn't just a logical process
Learned something new?
Read more Software Engineering Lessons from Production
I write articles with real insight into the career and skills of a modern software engineer. "Raw and honest from the heart!" as one reader described them. Fueled by lessons learned over 20 years of building production code for side-projects, small businesses, and hyper growth startups. Both successful and not.
Subscribe below 👇
Software Engineering Lessons from Production
Join Swizec's Newsletter and get insightful emails 💌 on mindsets, tactics, and technical skills for your career. Real lessons from building production software. No bullshit.
"Man, love your simple writing! Yours is the only newsletter I open and only blog that I give a fuck to read & scroll till the end. And wow always take away lessons with me. Inspiring! And very relatable. 👌"
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 ❤️