Home
Oldest
Hey everyone and welcome to this new community! Pardon the rough edges as I work out the kinks. Pro tip - head into the Settings and tweak the email notifications to just the ones you want!
Our plan this month:
Our plan this month:
- Ship Handbook v1.2 update
- Oct 4 - Guest Interview: Tech Resumes - Gergely Orosz
- Oct 10 2pm ET - Creator Workshop (Guest): Alex West
- Oct 24 12pm ET - Community Call
- Oct 31 12pm ET - Creator Workshop: Writing Your First Book
We are meeting at Clarke Quay, Sunday at 7pm - dinner group is full already but comment if you want to join for drinks after!
We were limited to 5 by Covid rules but it was good to meet up in person @ Ikki Izakaya!
I don't know about. you, but I am busy enough where I constantly forget to do the "public" part because I'm so busy executing.
Do you try to post something daily? Or have a pattern you follow so you remember to share something?
I feel like daily is a bit much but I also wonder if it "counts" if I don't post absolutely everything with full transparency π
Do you try to post something daily? Or have a pattern you follow so you remember to share something?
I feel like daily is a bit much but I also wonder if it "counts" if I don't post absolutely everything with full transparency π
Chaos Eng is a fascinating idea (and also a hella cool job title). The principal authors just released their book for free:
https://www.verica.io/the-chaos-engineering-book/ (has email signup, this was my link https://www.verica.io/e-book-download/?key=key5f9753ca9fe539.88705483&i=0)
https://www.verica.io/the-chaos-engineering-book/ (has email signup, this was my link https://www.verica.io/e-book-download/?key=key5f9753ca9fe539.88705483&i=0)
Hey all! I'm trying to do a local meetup in Philly when it's more safe to do so, if you're interested please shoot me a message or comment below!
I'll notify everyone once we set a date
I'll notify everyone once we set a date
Was writing this in a reply but I think it's so simple yet powerful that it's worth highlighting. By nature I'm reticent to spotlight myself and I get serious whoDoIThinkIAm-itis whenever I discourse with peers.
However, recently I watched Jeff Atwood's How To Stop Sucking And Be Awesome Instead where this point resonated:
However, recently I watched Jeff Atwood's How To Stop Sucking And Be Awesome Instead where this point resonated:
If your thing in public isn't awesome enough that's okay. People basically don't remember the things that you posted that weren't that useful to them, as long as they weren't harmful. The important thing is they do remember successes intensely. In fact they forget all your failures immediately and they go right to your successesβ that's all you'll be remembered for so just bear that in mind. That's the way people's minds work: they remember the things you did that helped them and then they'll very, very conveniently forget all the things you did that weren't that interesting.
the only thing i'm sure of is that zero hustle is definitely underselling yourself. our internet culture/economy inherently rewards people who put themselves out there, doubly so if you show up every day and people can see your authentic growth.
I think they pair together powerfully to make you think "why aren't I learning in public more?"
Max Rosen wrote this today: maxrozen.com/keeping-up-with-react-li... and I think it is such a dead simple idea for LIP I am jealous I didn't think of it earlier. (Edit: I guess it's a form of Open Source Knowledge)
The point is whenever you are part of an ecosystem, you have to learn about the various libraries and options anyway. Instead of keeping tabs in your head, write it down. Update it as time passes. Keep sending people to that page when they ask whats available. It is such a good lead magnet for your blog, plus it is a resource that improves your productivity when you need something (just like my spark-joy repo).
The point is whenever you are part of an ecosystem, you have to learn about the various libraries and options anyway. Instead of keeping tabs in your head, write it down. Update it as time passes. Keep sending people to that page when they ask whats available. It is such a good lead magnet for your blog, plus it is a resource that improves your productivity when you need something (just like my spark-joy repo).
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!
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Β