-
Author: Shawn Wang
-
Full Title: Learn in Public: The Fastest Way to Learn
-
Tags:: Learning in public
-
Highlights first synced by Readwise 2020-12-14
- 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 Discord, 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. (View Highlight)
- Learning Exhaust
- by far the biggest beneficiary of you trying to help past you is future you (View Highlight)
- 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, from scratch, to see how they work.
Teach workshops.
Go to conferences and summarize what you learned. (View Highlight)
- Try your best to be right, but don’t worry when you’re wrong. Repeatedly. If you feel uncomfortable, or like an impostor, good. You’re pushing yourself. (View Highlight)
- Wear your noobyness on your sleeve. (View Highlight)
- 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.
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? (View Highlight)