Learn in Public

Key Takeaways

• Create a system of information and knowledge that is helpful to a version of you from the past. You are learning in public, but are not creating FOR them or their approval. They can critique and assist but not hold you back
  You are working for future you, not teaching the world
• You are inviting the critiques, assistance, and correction of the public into your system. Do not be dismissive, be mindful and open to learning.

Atomic Idea Sparks

• At it's core, LIP is build on collaboration

It is a PERSONAL knowledge base, sure, but we don't know what we don't know, so by inviting the expertise of others, we are able to learn more than we could on our own, therefore becoming better than we could have alone

Critical Engagement

• Agreements

Collaboration is key. We cannot be afraid of growth or competition

• Tensions & Contradictions

This almost borderline feels like it is a launching pad for "You can start that business" or "You can change your life if you just do this one thing" kind of language. This is taken in a vacuum so I can't back that up, but I am not putting that on the author, but a lot of this information did sound like fluff, or a pep talk. But that could also be because this content seemed to be geared toward coders/tech bros specifically and the rest of us tangentially.

• Gaps & Open Questions

See Also

• Jeff Atwood: How to stop sucking and be awesome instead