Merge branch 'main' of https://github.com/davidgasquez/handbook

Communication.md

@@ -8,11 +8,12 @@ Communication is the science of transmitting knowledge to other humans. It goes
 
 - **You can not not communicate**. Not discussing the elephant in the room is communicating. Few things are as important to study, practice, and perfect as clear communication.
 - Whenever possible, communicate directly with those you're addressing rather than passing the message through intermediaries.
-- Communication between [a large group](https://twitter.com/RichRogers_/status/1159872097205805056) is hard. Noise in the processes might change the message and cause conflicts.  Nuance is hard to convey in groups. Some simple things to enhance communications:
+- Communication between [a large group](https://twitter.com/RichRogers_/status/1159872097205805056) is hard. Noise in the processes might change the message and cause conflicts.  Nuance is hard to convey in groups. 
+- Some tips to simplify communications:
 	- Use a few bullet points to put attention on the main points you want to convey.
 	- Without going overboard, use a tasteful amount of graphic design (e.g: bolding one key sentence).
 	- Break up a giant nuanced block into sections.
-	- If something is critical, make it visual: a picture, explainer video, or an infographic can be really useful for something key.
+	- If something is critical, make it visual.
 - If you want an answer, you have to [[Asking Questions | ask a question]]. People typically have a lot to say, but they'll volunteer little.
 
 ## Resources

DAOs.md

@@ -2,6 +2,7 @@
 
 - A Decentralized Autonomous Organization is a mechanism that enables online communities to form and coordinate economically.
 - DAOs make it possible for an online group with members from anywhere in the world to pool capital and hard-code rules — entirely in software — for how that capital will be managed and deployed. Those rules are then enforced by the underlying blockchain.
+- https://kernel.community/en/learn/
 - https://linda.mirror.xyz/Vh8K4leCGEO06_qSGx-vS5lvgUqhqkCz9ut81WwCP2o
 - https://mirror.xyz/danwu.eth/lDJxHnpjwo2m0_IF37jlyxOA_MB4SR_penTvntMLPHQ
 - https://foundation.app/blog/everything-you-need-to-know-about-daos

Dungeons and Dragons.md

@@ -8,3 +8,4 @@ Dungeons & Dragons is a cooperative storytelling game that harnesses your imagin
 - [Astral](https://www.astraltabletop.com/) - The easiest way to play tabletop role playing games online, free.
 - [Cyanomys' Guide To Playing RPGs Online](https://paper.dropbox.com/doc/Cyanomys-Guide-To-Playing-RPGs-Online-v2.1.0-Ef83ststlhPqW0LELrgye#:h2=Cyanomys%E2%80%99-Guide-To-Playing-RPG).
 - [5e.tools](https://5e.tools/index.html).
+- [Procedural Dungeon Generator](https://watabou.itch.io/one-page-dungeon) and other [procedural generators](https://watabou.itch.io/).

Hobbies.md

@@ -1,13 +1,13 @@
 # Hobbies
 
 - [[Pixel Art]]
-- [[Dungeons and Dragons]]
 - [[Piano]]
 - [[Podcasts]]
 - [[YouTube Channels]]
 - [[Personal Handbooks]]
 - [[Company Handbooks]]
 - [[Web Based Tools]]
+- [[Dungeons and Dragons]]
 - [[Recipes]]
 - [[Datathons]]
 

Ideas.md

@@ -77,6 +77,7 @@ A tool and framework to manage knowledge. This will allow compound learning and
 Instead of building the tool, we can start with a standard protocol and let other tools (Roam, Notion, Obsidian) use that.
 
 ### Open Source Projects
+
 - [Logseq](https://logseq.com/).
 - [Dendron](https://www.dendron.so/).
 - [Foam](https://foambubble.github.io/).

Life Advice.md

@@ -11,7 +11,6 @@ If you listen to successful people talk about their approaches, remember that al
 2. It is actionable
 3. It is based on some true insight
 
-
 ## Resources
 
 - [100 Ways To Live Better](https://www.lesswrong.com/posts/HJeD6XbMGEfcrx3mD/100-ways-to-live-better).

Pixel Art.md

@@ -4,5 +4,5 @@
 
 ## Resources
 
-- [PixelMe](https://pixel-me.tokyo/en/)
-- [PixelIt](https://giventofly.github.io/pixelit/)
+- [PixelMe](https://pixel-me.tokyo/en/) - Convert your photo into pixelart.
+- [PixelIt](https://giventofly.github.io/pixelit/) - Create pixel art from an image.

Planning.md

@@ -12,7 +12,7 @@ The goal of planning is to get to a unified and realistic plan for what the syst
 
 To help with planning, you should have these things:
 - Longterm Vision Statement. Where are you going.
-- Roadmap. A unified view of what the team is working towards shipping.
+- [[Writing a Roadmap | Roadmap]]. A unified view of what the team is working towards shipping.
 - List of options.
 
 No matter what the final plan is, [[Teamwork#^473cb4 | document it]] and you'll have a log of all the plans to reflect back on.

Podcasts.md

@@ -3,11 +3,11 @@
 You can explore all the podcast I'm subscribed to in [my PocketCast list](https://lists.pocketcasts.com/e0b1036d-ffe3-42af-ba4e-2c13a120a2b3). These are some of my favorite ones:
 
 - [Lex Fridman Podcast](https://lexfridman.com/podcast/). Conversations about science, technology, history, philosophy and the nature of intelligence, consciousness, love, and power.
-- [Made You Think](https://madeyouthinkpodcast.com/). Episodes will explore books, essays, podcasts, and anything else that warrants further discussion, teaches something useful, or at the very least, exercises our brain muscles.
-- [Hardcore History](https://www.dancarlin.com/hardcore-history-series/). Explores topics throughout world history.
-- [The Knowledge Project](https://fs.blog/knowledge-project/). Helps you master the best of what other people have already figured out.
-- [The Tim Ferriss Show](https://tim.blog/podcast/). He deconstruct world-class performers from eclectic areas (investing, sports, business, art, etc.) to extract the tactics, tools, and routines you can use.
 - [Cortex](https://www.relay.fm/cortex). CGP Grey and Myke Hurley get together to discuss their working lives.
+- [Hardcore History](https://www.dancarlin.com/hardcore-history-series/). Explores topics throughout world history.
+- [Made You Think](https://madeyouthinkpodcast.com/). Episodes will explore books, essays, podcasts, and anything else that warrants further discussion, teaches something useful, or at the very least, exercises our brain muscles.
+- [Mindscape](https://www.preposterousuniverse.com/podcast/). Conversations with the world's most interesting thinkers. Science, society, philosophy, culture, arts, and ideas.
 - Spanish.
+- [Fall of Civilizations](https://fallofcivilizationspodcast.com/). A podcast that explores the collapse of different societies through history.
   - [Gabinete de Curiosidades](https://www.gabinetepodcast.com/).
   - [Kaizen](https://www.jaimerodriguezdesantiago.com/).

Programming.md

@@ -1,6 +1,7 @@
 # Programming
 
 A programmer should know [lots](http://programmer.97things.oreilly.com/wiki/index.php/Contributions_Appearing_in_the_Book) [of](http://www.artima.com/weblogs/viewpost.jsp?thread=331531) [concepts](http://programmer.97things.oreilly.com/wiki/index.php/Other_Edited_Contributions). Try to keep in mind the following principles:
+
 - **Small is beautiful**.
 	- Small things have tremendous advantages over their larger counterparts. Among these is the ability to combine with other small things in unique and useful ways.
 	- The best code is no code, or code you don’t have to maintain.
@@ -9,7 +10,6 @@ A programmer should know [lots](http://programmer.97things.oreilly.com/wiki/inde
 	- Benefits of simplicity: ease of understanding, ease of change, ease of debugging, flexibility. [The goal of software design is to create chunks or slices that fit into a human mind](https://mobile.twitter.com/KentBeck/status/1354418068869398538). The software keeps growing but the human mind maxes out, so we have to keep chunking and slicing differently if we want to keep making changes.
 	- We can't change our brain to grasp something complex. We need to simplify complexity so we can handle it.
 	- Eliminate state. If you can’t, make it visible.
-	- Writing program code is a good way of debugging your thinking.
 	- Design is an iterative process. The necessary number of iterations is one more than the number you have currently done. This is true at any point in time.
 	- Complexity is the single major difficulty in the successful development of large-scale software systems.
 	- Write code that's easy to delete.
@@ -19,6 +19,7 @@ A programmer should know [lots](http://programmer.97things.oreilly.com/wiki/inde
 	- Build a prototype as soon as possible to get a sense of the entire process.
 	- Once you have a working prototype, apply guidelines and previous learnings.   Then, focus on performance.
 	- There is nothing so useless as doing efficiently that which should not be done at all.
+	- Writing program code is a good way of debugging your thinking.
 	- Apply small improvements at each iteration. Running the program will make it more resilient and robust as more errors get fixed.
 	- Premature optimization is the root of all evil. Abstraction is a form of optimization and shouldn't be done before the space has been properly explored to know what abstractions should be built. Standardization is a form of optimization and shouldn't be proposed until there's a body of evidence to support what's being standardized.
 	- Sometimes you have to stop sharpening the saw, and just start cutting.

Presentation Rules.md → Public Speaking.md

@@ -1,10 +1,11 @@
-# Presentation Rules
+# Public Speaking
 
 Some great advice for [public speaking presentations](http://www.jilles.net/perma/2020/06/05/presentation-rules.html):
 
+- Start the presentation with a set of questions that will be answered through the presentation. Start with an empowerment promise. Outline what the audience will know by the end of the talk.
 - Find a way to connect with the audience right away.
 - Don't expose one bullet point of a list at a time. Your audience will ask to go back a slide or two, you end up half way in a build, or worse, with an empty slide. None of this is needed.
-- Don't just read the words on a page or sound like you’re delivering a memorized speech
+- Don't just read the words on a page or sound like you’re delivering a memorized speech.
 - [The best talks are stories. The best stories involve repetition.](https://speakerdeck.com/holman/the-talk-on-talks) Tell a personal story to make your ideas more sticky.
 - Anticipate the audience’s skepticism and use it to your advantage.
 - Use fewer words. There is a place for details and context, but the most important is the actual message you want to get across.
@@ -13,7 +14,6 @@ Some great advice for [public speaking presentations](http://www.jilles.net/perm
 - Number the slides.
 - Don't present any slide with a wall of text.
 - Titles for the graphs should be the conclusion.
-- Start the presentation with a set of questions that will be answered through the presentation.
 
 ## Resources
 

Relationships.md

@@ -1,12 +1,6 @@
 # Relationships
 
-Tested advice for improving the chances of relationship success and satisfaction include:
-1. Do novel and exciting things with your partner often.
-2. Say positive things to and about your partner at least 5 times more often than you say negative things.
-3. Spend each week writing about why your relationship is better than some others you know about.
-4. Qualify every criticism of your partner with a review of one or two of their positive qualities.
-
-
-Some random tips:
 - Have fun with the people you love.
 - Build small groups. Small communities do more things that larger ones.
+- Do novel and exciting things with your friends often.
+- Create many contexts. A friend who you see in only one context is likely to be a less close friend than someone who you see in many contexts, and connect with over many different things, rather than a single shared interest.

Writing.md

@@ -17,7 +17,7 @@
   - Declare and reject the antithesis.
   - Conclusions.
 - Use positive language rather than negative language.
-- Human beings are wired to respond to storytelling. A story arc is a way to structure ideas to tap into this response, typically by describing a change in the world. This applies to everything, e.g: [[Presentation Rules]]
+- Human beings are wired to respond to storytelling. A story arc is a way to structure ideas to tap into this response, typically by describing a change in the world. This applies to everything, e.g: [[Public Speaking]]
 - Don't fully think through your ideas before writing. It's inefficient. The best way to think is by writing. It compels your brain to connect the dots. [Write whatever helps you think better](https://twitter.com/eugeneyan/status/1256828197410201601).
 - [Don’t try to _persuade_ people that the idea is true/good. Instead, try to accurately _describe_ where the idea came from, the path which led _you_ to think it’s true/plausible/worth a look. In the process, you’ll probably convey your own actual level of uncertainty, which is exactly the right thing to do.](https://www.lesswrong.com/posts/Psr9tnQFuEXiuqGcR/how-to-write-quickly-while-maintaining-epistemic-rigor)
 - Separate the processes of creation from improving. **You can't write and edit**. Write the first draft fast, then iterate on it editing things. Much of this editing will be cutting, and that makes simple writing even simpler.