davidgasquez.com
📚 Personal bits of knowledge
docs: ✏️ update links for accuracy and improve content across multiple documents
Revised various documents to enhance accuracy and clarity by updating outdated links to archived versions. Changes include updates in Asking Questions.md, Decentralized Autonomous Organizations.md, Decentralized Web.md, Design Docs.md, Making Decisions.md, Open Data.md, Podcasts.md, Teamwork.md, and Writing a Roadmap.md. Additionally, modified link checker arguments in links.yml to improve error handling during checks, ensuring better workflow efficiency.
+1
-1
.github/workflows/links.yml
+1
-1
.github/workflows/links.yml
+1
-1
Asking Questions.md
+1
-1
Asking Questions.md
···
8
3. Be explicit about what you want to achieve in the end and provide as much up-front information as possible to help.
9
4. Respect other people's [[time]]. Follow up after you get an answer.
10
- [When asking for help, let the people know what the problem you are trying to solve actually is instead of simply saying your solution and the reader guessing what it is you are actually trying to do](http://xyproblem.info/).
11
-
- [Think about the question like a child](https://www.aaronkharris.com/asking-questions).
12
- The most simple, seemingly silly questions are almost always profound.
13
- Good questions must come from a sincere desire to learn, rather than as a veiled means of stating your own opinion.
···
8
3. Be explicit about what you want to achieve in the end and provide as much up-front information as possible to help.
9
4. Respect other people's [[time]]. Follow up after you get an answer.
10
- [When asking for help, let the people know what the problem you are trying to solve actually is instead of simply saying your solution and the reader guessing what it is you are actually trying to do](http://xyproblem.info/).
11
+
- [Think about the question like a child](https://web.archive.org/web/20210115231031/https://www.aaronkharris.com/asking-questions).
12
- The most simple, seemingly silly questions are almost always profound.
13
- Good questions must come from a sincere desire to learn, rather than as a veiled means of stating your own opinion.
-1
Decentralized Autonomous Organizations.md
-1
Decentralized Autonomous Organizations.md
-2
Decentralized Web.md
-2
Decentralized Web.md
···
17
- [Trello](https://dework.xyz/)
18
- [Notion](https://www.clarity.so/)
19
- [Medium](https://mirror.xyz/dashboard)
20
-
- [Search](https://slate.host/)
21
- [Imgur](https://www.pinata.cloud/)
22
- [Netlify](https://fleek.co/)
23
- [Firebase](https://textile.io)
···
95
### Bounty Based Collaboration
96
97
- [Bounties Network](https://bounties.network/) - Find freelancers and bounty programs for any task paid in any token on Ethereum.
98
-
- [Open Bounty](https://openbounty.status.im/) - Bounty-based collaboration tool that plugs right into GitHub.
99
- [Gitcoin](https://gitcoin.co/) - The easiest way to leverage the open source community to incentivize or monetize work.
100
- [Inmunefy](https://immunefi.com/) - Web3's leading bug bounty platform, protecting $100 billion in user funds.
101
- [DAOexchange](https://daoexchange.app/). Cross-DAO bounty board.
···
17
- [Trello](https://dework.xyz/)
18
- [Notion](https://www.clarity.so/)
19
- [Medium](https://mirror.xyz/dashboard)
20
- [Imgur](https://www.pinata.cloud/)
21
- [Netlify](https://fleek.co/)
22
- [Firebase](https://textile.io)
···
94
### Bounty Based Collaboration
95
96
- [Bounties Network](https://bounties.network/) - Find freelancers and bounty programs for any task paid in any token on Ethereum.
97
- [Gitcoin](https://gitcoin.co/) - The easiest way to leverage the open source community to incentivize or monetize work.
98
- [Inmunefy](https://immunefi.com/) - Web3's leading bug bounty platform, protecting $100 billion in user funds.
99
- [DAOexchange](https://daoexchange.app/). Cross-DAO bounty board.
+1
-1
Design Docs.md
+1
-1
Design Docs.md
···
6
- Short specs are more likely to be read. The purpose of a spec is to briefly communicate the "why", "what" and "how" of the project to the rest of the team. Ideally these short documents force teams to scope out work so priorities are clear and teams avoid building the wrong thing.
7
- [The longer your document is, the more likely people will only read the comments and not the body.](https://twitter.com/hamiltonulmer/status/1562817324184440832)
8
- A tech spec forces you to think through complicated issues and to get everyone on the same page. This helps to avoid wasting time on dead-end solutions or building the wrong thing.
9
-
- It's hard to make technical decisions while remote. [Build a Proposal Culture](https://hamiltonulmer.com/writing/building-a-proposal-culture) to enable effective distributed technical decision making via [[Writing]] and collecting [[Feedback]] on a written document in an inclusive, async-friendly way.
10
- Even if no one else reads them, they force you to clarify my thinking before you start the (more expensive) process of implementation.
11
- Design docs fulfill the following functions in the software development life-cycle:
12
- Early identification of design issues when making changes is still cheap.
···
6
- Short specs are more likely to be read. The purpose of a spec is to briefly communicate the "why", "what" and "how" of the project to the rest of the team. Ideally these short documents force teams to scope out work so priorities are clear and teams avoid building the wrong thing.
7
- [The longer your document is, the more likely people will only read the comments and not the body.](https://twitter.com/hamiltonulmer/status/1562817324184440832)
8
- A tech spec forces you to think through complicated issues and to get everyone on the same page. This helps to avoid wasting time on dead-end solutions or building the wrong thing.
9
+
- It's hard to make technical decisions while remote. [Build a Proposal Culture](https://web.archive.org/web/20220925011031/https://www.hamiltonulmer.com/writing/building-a-proposal-culture) to enable effective distributed technical decision making via [[Writing]] and collecting [[Feedback]] on a written document in an inclusive, async-friendly way.
10
- Even if no one else reads them, they force you to clarify my thinking before you start the (more expensive) process of implementation.
11
- Design docs fulfill the following functions in the software development life-cycle:
12
- Early identification of design issues when making changes is still cheap.
+1
-1
Making Decisions.md
+1
-1
Making Decisions.md
···
43
- If you're in between two decisions, don't half-ass both of them! Do one 100%, then do the other 100%.
44
- People reason more wisely about other people's problems than about their own.
45
- When you share something, add the level of confidence you have on it.
46
-
- [Understand your personal stance on the trade-off of compromise versus purity](https://vitalik.ca/general/2020/11/08/concave.html). Given a choice between two alternatives, often both expressed as deep principled philosophies, do you naturally gravitate toward the idea that one of the two paths should be correct and we should stick to it, or do you prefer to find a way in the middle between the two extremes?
47
- [It's often not _how much force_ you can bring to bear, so much as whether you can apply that force _effectively_](https://www.lesswrong.com/posts/rQKstXH8ZMAdN5iqD/concentration-of-force).
48
49
···
43
- If you're in between two decisions, don't half-ass both of them! Do one 100%, then do the other 100%.
44
- People reason more wisely about other people's problems than about their own.
45
- When you share something, add the level of confidence you have on it.
46
+
- [Understand your personal stance on the trade-off of compromise versus purity](https://vitalik.eth.limo/general/2020/11/08/concave.html). Given a choice between two alternatives, often both expressed as deep principled philosophies, do you naturally gravitate toward the idea that one of the two paths should be correct and we should stick to it, or do you prefer to find a way in the middle between the two extremes?
47
- [It's often not _how much force_ you can bring to bear, so much as whether you can apply that force _effectively_](https://www.lesswrong.com/posts/rQKstXH8ZMAdN5iqD/concentration-of-force).
48
49
+1
-1
Open Data.md
+1
-1
Open Data.md
···
227
228
### Data Package Managers
229
230
-
- [Qri](https://qri.io/). An evolution of the classical open portals that added [[Decentralized Protocols]] (IPFS) and computing on top of the data. Sadly, [it came to an end early in 2022](https://qri.io/winding_down).
231
- [Datalad](https://www.datalad.org/). [Extended to IPFS](https://kinshukk.github.io/posts/gsoc-summary-and-future-thoughts/)
232
- Is a [great tool](https://archive.fosdem.org/2020/schedule/event/open_research_datalad/) and uses Git Annex (distributed binary object tracking layer on top of git).
233
- Complicated to wrap your head around. Lots of different commands and concepts. On the other hand, it's very powerful and flexible. Git Annex is complex but powerful and flexible.
···
227
228
### Data Package Managers
229
230
+
- [Qri](https://web.archive.org/web/20240413160218/https://qri.io/). An evolution of the classical open portals that added [[Decentralized Protocols]] (IPFS) and computing on top of the data. Sadly, [it came to an end early in 2022](https://qri.io/winding_down).
231
- [Datalad](https://www.datalad.org/). [Extended to IPFS](https://kinshukk.github.io/posts/gsoc-summary-and-future-thoughts/)
232
- Is a [great tool](https://archive.fosdem.org/2020/schedule/event/open_research_datalad/) and uses Git Annex (distributed binary object tracking layer on top of git).
233
- Complicated to wrap your head around. Lots of different commands and concepts. On the other hand, it's very powerful and flexible. Git Annex is complex but powerful and flexible.
+1
-1
Podcasts.md
+1
-1
Podcasts.md
···
9
- [Mindscape](https://www.preposterousuniverse.com/podcast/). Conversations with the world's most interesting thinkers. Science, society, philosophy, culture, arts, and ideas.
10
- Spanish.
11
- [Fall of Civilizations](https://fallofcivilizationspodcast.com/). A podcast that explores the collapse of different societies through history.
12
-
- [Gabinete de Curiosidades](https://www.gabinetepodcast.com/).
13
- [Kaizen](https://www.jaimerodriguezdesantiago.com/).
···
9
- [Mindscape](https://www.preposterousuniverse.com/podcast/). Conversations with the world's most interesting thinkers. Science, society, philosophy, culture, arts, and ideas.
10
- Spanish.
11
- [Fall of Civilizations](https://fallofcivilizationspodcast.com/). A podcast that explores the collapse of different societies through history.
12
+
- [Gabinete de Curiosidades](https://web.archive.org/web/20240528141801/https://www.gabinetepodcast.com/).
13
- [Kaizen](https://www.jaimerodriguezdesantiago.com/).
+1
-1
README.md
+1
-1
README.md
···
4
5
Personal bits of living knowledge, open for everyone.
6
7
-
- 🛠️ Explore [this Handbook on GitHub](https://github.com/davidgasquez/handbook). Send a [Pull Request](https://github.com/davidgasquez/handbook/pulls) or [fill an issue](https://github.com/davidgasquez/handbok/issues) if you have any feedback!
8
- 🗺️ Explore any topic you find interesting on the left sidebar.
9
- 📣 [Reach out](https://davidgasquez.com/) if you want to chat!
10
···
4
5
Personal bits of living knowledge, open for everyone.
6
7
+
- 🛠️ Explore [this Handbook on GitHub](https://github.com/davidgasquez/handbook). Send a [Pull Request](https://github.com/davidgasquez/handbook/pulls) or [fill an issue](https://github.com/davidgasquez/handbook/issues) if you have any feedback!
8
- 🗺️ Explore any topic you find interesting on the left sidebar.
9
- 📣 [Reach out](https://davidgasquez.com/) if you want to chat!
10
+2
-2
Teamwork.md
+2
-2
Teamwork.md
···
16
- Automated code formatting.
17
- Templates for new projects and components.
18
- Mechanisms for creating test data.
19
-
- Invest in [thoughtful logging](https://www.16elt.com/2023/01/06/logging-practices-I-follow/a).
20
- Create a [[Company Handbooks|handbook]] to store your [[Company Knowledge Management|company knowledge]]. Document:
21
- [[Processes]]. Status updates, [[Design Docs]], [on-boarding docs/scripts](https://about.gitlab.com/blog/2020/02/10/lessons-learned-as-data-team-manager/), [[Checklist]], ...
22
- Decisions. Context and rationale can be documented in a durable location.
···
28
- Responsibilities. Things that aren't your fault can still be your responsibility. If something is everyone's job, it's no one's job.
29
- Defaults. Each thing should have a place by default, docs, issues, ...
30
- Aim to be a completely autonomous team. Everyone should feel empower to make decisions. Those who are responsible for something must have the means and context to effect it. You build it, you run it! **The company strategy guides the team, it doesn't tell it what to do.
31
-
- [A team's ability to operate autonomously relies on alignment, which is strengthened by context](https://macroapp.io/blog/the-context-warehouse).
32
- You can also have no durable cross-functional teams. Teams assemble around a project and disperse once the project is done.
33
- Run [Automated Check-ins](https://basecamp.com/features/checkins) to share things explicitly. What are people working on, what are they planning to work on next, ...
34
- The right way to promote people is to give them [meaningful and clear goals](https://youtu.be/oIMvMb5wVO4) for the organization and promote them if they hit the goals.
···
16
- Automated code formatting.
17
- Templates for new projects and components.
18
- Mechanisms for creating test data.
19
+
- Invest in [thoughtful logging](https://www.16elt.com/2023/01/06/logging-practices-I-follow/).
20
- Create a [[Company Handbooks|handbook]] to store your [[Company Knowledge Management|company knowledge]]. Document:
21
- [[Processes]]. Status updates, [[Design Docs]], [on-boarding docs/scripts](https://about.gitlab.com/blog/2020/02/10/lessons-learned-as-data-team-manager/), [[Checklist]], ...
22
- Decisions. Context and rationale can be documented in a durable location.
···
28
- Responsibilities. Things that aren't your fault can still be your responsibility. If something is everyone's job, it's no one's job.
29
- Defaults. Each thing should have a place by default, docs, issues, ...
30
- Aim to be a completely autonomous team. Everyone should feel empower to make decisions. Those who are responsible for something must have the means and context to effect it. You build it, you run it! **The company strategy guides the team, it doesn't tell it what to do.
31
+
- [A team's ability to operate autonomously relies on alignment, which is strengthened by context](https://web.archive.org/web/20230605055308/https://macroapp.io/blog/the-context-warehouse).
32
- You can also have no durable cross-functional teams. Teams assemble around a project and disperse once the project is done.
33
- Run [Automated Check-ins](https://basecamp.com/features/checkins) to share things explicitly. What are people working on, what are they planning to work on next, ...
34
- The right way to promote people is to give them [meaningful and clear goals](https://youtu.be/oIMvMb5wVO4) for the organization and promote them if they hit the goals.
+1
-1
Writing a Roadmap.md
+1
-1
Writing a Roadmap.md
···
1
# Writing a Roadmap
2
3
-
[Setting direction is one of the most important things you'll do when building a product and company. A clear direction aligns everyone to work toward the same goals](https://linear.app/method/roadmap). It helps individuals make daily decisions, teams prioritize projects and all members of your organization feel motivated toward a shared purpose. Without direction, it's harder to work together, know what to focus on and make meaningful progress.
4
5
Best practices to follow when building and managing a roadmap:
6
···
1
# Writing a Roadmap
2
3
+
[Setting direction is one of the most important things you'll do when building a product and company. A clear direction aligns everyone to work toward the same goals](https://web.archive.org/web/20240423211458/https://linear.app/method/roadmap). It helps individuals make daily decisions, teams prioritize projects and all members of your organization feel motivated toward a shared purpose. Without direction, it's harder to work together, know what to focus on and make meaningful progress.
4
5
Best practices to follow when building and managing a roadmap:
6