|
12345 |
- title: Learn In Public
- url: https://www.swyx.io/writing/learn-in-public/
- hash_url: 079e037d172796798451cbba9da82cb9
-
- <p>If there's a golden rule, it's this one, so I put it first. All the other rules are more or less elaborations of this rule #1.</p> <p>You already know that you will never be done learning. But most people "learn in private", and lurk. They consume content without creating any themselves. Again, that's fine, but we're here to talk about being in the top quintile. What you do here is to have a habit of creating learning exhaust. Write blogs and tutorials and cheatsheets. Speak at meetups and conferences. Ask and answer things on Stackoverflow or Reddit. (Avoid the walled gardens like Slack and Discourse, they're not public). Make Youtube videos or Twitch streams. Start a newsletter. Draw cartoons (people loooove cartoons!). Whatever your thing is, make the thing you wish you had found when you were learning. Don't judge your results by "claps" or retweets or stars or upvotes - just talk to yourself from 3 months ago. I keep an almost-daily dev blog written for no one else but me.</p> <p>Guess what? It's not about reaching as many people as possible with your content. If you can do that, great, remember me when you're famous. But chances are that by far the biggest beneficiary of you trying to help past you is future you. If others benefit, that's icing.</p> <p>Oh you think you're done? Don't stop there. Enjoyed a coding video? Reach out to the speaker/instructor and thank them, and ask questions. Make PR's to libraries you use. Make your own libraries no one will ever use. Clone stuff you like. Teach workshops. Go to conferences and summarize what you learned. Heck, go back to your own bootcamp to tell alumni what's worked for you. There's always one level deeper. But at every step of the way: Document what you did and the problems you solved.</p> <p>The subheading under this rule would be: <strong>Try your best to be right, but don't worry when you're wrong.</strong> Repeatedly. If you feel uncomfortable, or like an impostor, good. You're pushing yourself. Don't assume you know everything, but try your best anyway, and let the internet correct you when you are inevitably wrong. Wear your noobyness on your sleeve.</p> <p>People think you suck? Good. You agree. Ask them to explain, in detail, why you suck. You want to just feel good or you want to <strong>be</strong> good? No objections, no hurt feelings. Then go away and prove them wrong. Of course, if they get abusive block them.</p> <p>Did I mention that teaching is the best way to learn? Talk while you code. It can be stressful and I haven't done it all that much but my best technical interviews have been where I ended up talking like I teach instead of desperately trying to prove myself. We're animals, we're attracted to confidence and can smell desperation.</p> <p>At some point you'll get some support behind you. People notice genuine learners. They'll want to help you. Don't tell them, but they just became your mentors. This is very important: <em>Pick up what they put down</em>. Think of them as offering up quests for you to complete. When they say "Anyone willing to help with <strong>__</strong> <strong>__</strong>?" you're that kid in the first row with your hand already raised. These are senior engineers, some of the most in-demand people in tech. They'll spend time with you, 1 on 1, if you help them out (p.s. and there's always something they want help on). You can't pay for this stuff. They'll teach you for free. Most people don't see what's right in front of them. But not you.</p> <p>"With so many junior devs out there, why will they help <em>me</em>?", you ask.</p> <p>Because you learn in public. By teaching you they teach many. You amplify them. You have one thing they don't: a beginner's mind. You see how this works?</p> <p>At some point people will start asking you for help because of all the stuff you put out. 80% of developers are "dark", they dont write or speak or participate in public tech discourse. But you do. You must be an expert, right? Don't tell them you aren't. Answer best as you can, and when you're stuck or wrong pass it up to your mentors.</p> <p>Eventually you run out of mentors, and just solve things on your own. You're still putting out content though. You see how this works?</p> <p>Learn in public.</p> <p>p.s. Eventually, they'll want to pay you for your help too. A lot more than you think.</p>
|
