Home
Likes
Three fundamental truths:
- The expiry date of content varies wildly from seconds to centuries.
- Short-lived content is easier to make, therefore more easily available, than long-lived content.
- Our useful knowledge is determined by the sum total of *still relevant* content we remember. To a large approximation our knowledge only compounds by the proportion of long-lived content we remember.
The Lindy Effect observes that things that have been around for a while tend to live longer than things that haven't. A Lindy Library is an annex of content that has stood the test of time (say, more than 3 years old and still extremely relevant).
- Social media biases us towards consuming extremely new content that becomes irrelevant the next day.
- A Lindy Library corrects this bias by helping us spend our time on things we are likely to remember and use, thus compounding our knowledge from reading.
- By sharing our Lindy Library we extend this benefit to our friends.
You are welcome to submit technical and nontechnical content that meets this high bar, as long as it relates to developers and developer careers. However swyx may remove submissions at his discretion since curation is extremely important to the value of this effort.
More Lindy Libraries here:
- The Coding Career Handbook :)
- Leadership Library for Engineers
- Essays on Programming I think about a lot
- Timeless Web Dev Articles
- MIT Missing Semester
- LindyLibrary.org
- Fermats Library
- Hacker News Classics
- Distributed Systems Reading List, Muratbuffalo's foundational distsys papers
- Resources for Amateur Compiler Writers
- The expiry date of content varies wildly from seconds to centuries.
- Short-lived content is easier to make, therefore more easily available, than long-lived content.
- Our useful knowledge is determined by the sum total of *still relevant* content we remember. To a large approximation our knowledge only compounds by the proportion of long-lived content we remember.
The Lindy Effect observes that things that have been around for a while tend to live longer than things that haven't. A Lindy Library is an annex of content that has stood the test of time (say, more than 3 years old and still extremely relevant).
- Social media biases us towards consuming extremely new content that becomes irrelevant the next day.
- A Lindy Library corrects this bias by helping us spend our time on things we are likely to remember and use, thus compounding our knowledge from reading.
- By sharing our Lindy Library we extend this benefit to our friends.
You are welcome to submit technical and nontechnical content that meets this high bar, as long as it relates to developers and developer careers. However swyx may remove submissions at his discretion since curation is extremely important to the value of this effort.
More Lindy Libraries here:
- The Coding Career Handbook :)
- Leadership Library for Engineers
- Essays on Programming I think about a lot
- Timeless Web Dev Articles
- MIT Missing Semester
- LindyLibrary.org
- Fermats Library
- Hacker News Classics
- Distributed Systems Reading List, Muratbuffalo's foundational distsys papers
- Resources for Amateur Compiler Writers
DX Circle is an idea I had for learning in public about 3 aspects of developer experience I am keen on:
- Developer Tools
- Developer Communities
- Investing in Seed/Series A Startups that do either (DX Angels)
This arises out of my side jobs building developer communities (/r/reactjs and Svelte Society) and being an angel investor in devtools/community startups. I considered splitting this out into a separate community, but was unsure about how to do it, so this is my MVP.
Please feel free to mute this section if you are only here for Coding Career stuff. I won't hold back here.
Please feel free to mute this section if you are only here for Coding Career stuff. I won't hold back here.
- "What we should aim for is to take this staircase and if we provide enough information and answer enough questions and have enough meetups and are friendly and welcoming and give everyone a sense of belonging — then eventually these steps stop becoming barriers and we smooth it out and suddenly getting from zero to useful. It's not just the language either, it's all the tools and all the scripts and everything everybody publishes on GitHub.
if you have some really basic code that other people can read and learn from that's helpful. There's so many things that we could do.
If we learn in public then we're building a ramp for everyone who comes behind us.
An idea doesn't belong to one person — first of all it's pretty unlikely that only one person thought of it — but even that it doesn't belong to the first person who published it, it belongs with everyone who contributes to making that idea useful to the world.
Everyone who writes a script that makes the build process a little easier. Everyone who tweets about it and attracts some attention so that people say "huh, maybe I could use that".
Everyone who writes a blog post or an issue or contributes in any way is part of Elixir"
- Jessica Kerr at ElixirConf
Tiago Forte is mr. Second Brain, and this recaps a lot of his ideas in one 10x blogpost.
I'm a very strong advocate of summarizing books to Learn in Public, but beyond that this is really about how you process ANY content, from tweets to talks.
I'm a very strong advocate of summarizing books to Learn in Public, but beyond that this is really about how you process ANY content, from tweets to talks.
Decided to kick this learn in public thing up a notch and release a public website of my on-going notes. Let me know your thoughts!
https://hassansnotes.com/
https://hassansnotes.com/
A 4 part book series detailing the internals of basically every important OSS application in the world. I would love to form a book club around this someday!
People can learn in public by building things, but often need ideas for what to build. So here are a list of good projects to pursue:
- devchallenges.io/
- javascript30.com/
- /r/reactjs Project Ideas (i used to curate)
- Make React Apps (
Chris on Code
's paid course)
- Build Your Own X repo
- Max Rozen's open source React app list
anything else?
- devchallenges.io/
- javascript30.com/
- /r/reactjs Project Ideas (i used to curate)
- Make React Apps (
- Build Your Own X repo
- Max Rozen's open source React app list
anything else?
1. Start a Newsletter from 0 Subscribers
An awesome guide from Lesley here!
2. Learn In Public, but, like, said differently
Prompt:
Response:
3. Create a weekend project that helps others write better documentation
(Katherine got a job at GitHub 2 months later)
4. Create a great "Intro to X" video
P.S. Shoutout to
Ron Au
who's LIP work creating luck for himself got him an opportunity out of the blue
An awesome guide from Lesley here!
2. Learn In Public, but, like, said differently
Prompt:
(Katherine got a job at GitHub 2 months later)
4. Create a great "Intro to X" video
P.S. Shoutout to
Wanted to share my experience trying a new notetaking setup. In short, I was tired of all the anxiety around organizing everything I write down. Finding the perfect folder / page / service / tag for a note was enough of a blocker to avoid writing anything at all!
Still working out the kinks, but the Foam project for VS Code really ramped up my notetaking habits. It's also easily host-able as a Jekyll or 11ty site, if you want to learn in public (TM) 😁
Wrote a longer-form post over here. Curious what solutions work for y'all!
Still working out the kinks, but the Foam project for VS Code really ramped up my notetaking habits. It's also easily host-able as a Jekyll or 11ty site, if you want to learn in public (TM) 😁
Wrote a longer-form post over here. Curious what solutions work for y'all!
Jeff Zhang DM-ed me with the coolest story. As a University of Waterloo student, he was been practicing Learn in Public for a couple years after listening to swyx's podcast with Quincy Larson. He recently got a coveted internship working at Tesla, and attributes it to #LIP!
We recorded our conversation for other college students interested in starting this journey! It doesn't just cover the job, but also all of Jeff's questions on Learning in Public:
We recorded our conversation for other college students interested in starting this journey! It doesn't just cover the job, but also all of Jeff's questions on Learning in Public:
- the 4 Learning Gears
- Writing thoughts down makes you a more structured and eloquent speaker
- Absolute vs Relative Happiness
- Have ways to win even if nobody else joins you
- Linked to Stoicism
- Failing to get matched for a Google internship
- The 4 Months of Quiet
- Your relationships with people will outlast any job - invest in building relationships
- Creating Luck
- Veritasium - Success and Luck
- (32mins) Tesla story
- The problem with the industry bias for Portfolios and Resumes
- "You can impress most hiring managers with only 3 contribs" - Mekka Okereke
- Resumes are an extremely lossy human experience compression format
- Learn in Public is cryptographic "Proof of Work"
- My Livestream with Gergely Orosz - The Tech Resume Inside-Out
- Private Companies and #LearnInPublic
- Advice to Interns and New Grads
- By definition you are nonessential
- Be helpful
- Ask stupid questions - Lampshading
- THEN write it down!!!
- Compounding Open Source Knowledge
- Marketing Yourself
- The value of bringing your unique qualities to your creative inspiration
- Moral Panic and Technology Addiction
