chore: add files from master-wiki repo

This commit is contained in:
Alexander Navarro 2024-11-20 20:00:35 -03:00
parent f99a9ae2ac
commit 1847f6bf28
315 changed files with 1047341 additions and 0 deletions

View file

@ -0,0 +1,15 @@
---
created: 2024-02-10T18:24:25-03:00
modified: 2024-02-10T18:33:38-03:00
updated: 2024-03-12 13:49
---
# 12. Questions
1. ¿Cómo puedo automatizar una tarea tediosa y/o que consume mucho tiempo?
2. ¿Cómo me puedo hacer la vida más sencilla?
> You have to keep a dozen of your favorite problems constantly present in your mind, although by and large they will lay in a dormant state. Every time you hear or read a new trick or a new result, test it against each of your twelve problems to see whether it helps. Every once in a while there will be a hit, and people will say, “How did he do it? He must be a genius!”’
>
source: Tiago Forte, “[[Building a Second Brain]]”, p. 62

View file

@ -0,0 +1,9 @@
---
created: 2024-02-21 10:39
updated: 2024-03-12 13:49
---
An Archipelago of Ideas separates the two activities your brain has the most difficulty performing at the same time: _choosing_ ideas (known as selection) and _arranging_ them into a logical flow (known as sequencing).
The goal of an archipelago is that instead of sitting down to a blank page or screen and stressing out about where to begin, **you start with a series of small stepping-stones to guide your efforts**. First you select the points and ideas you want to include in your outline, and then in a separate step, you rearrange and sequence them into an order that flows logically. This makes both of those steps far more efficient, less taxing, and less vulnerable to interruption.
To create an Archipelago of _Ideas_, you divergently gather a group of ideas, sources, or points that will form the backbone of your essay, presentation, or deliverable. Once you have a critical mass of ideas to work with, you switch decisively into convergence mode and link them together in an order that makes sense.

File diff suppressed because one or more lines are too long

View file

@ -0,0 +1,10 @@
---
created: 2024-02-21 12:33
updated: 2024-03-12 13:49
---
## Examples:
- If you want to write a book, you could dial down the scope and write a series of online articles outlining your main ideas. If you dont have time for that, you could dial it down even further and start with a social media post explaining the essence of your message.
- If you want to deliver a workshop for paying clients, you could dial it down to a free workshop at a local meetup, or dial it down even further and start with a group exercise or book club for a handful of colleagues or friends.
- If youd like to make a short film, start with a YouTube video, or if thats too intimidating, a livestream. If its still too much, record a rough cut on your phone and send it to a friend.
- If you want to design a brand identity for a company, start with a mock-up of a single web page. Even easier, start with a few hand-drawn sketches with your ideas for a logo.

View file

@ -0,0 +1,31 @@
---
created: 2024-02-20 11:14
updated: 2024-03-12 13:49
---
# Habits to apply while notetaking process
In order to provide high quality work we need to be organized to be able to _go with the flow_ and have the less friction posible. But we cannot afford to stop everything in our life to organize our stuff, we need to continue delivering and taking care of the next _"important stuff"_ one after the other.
For this, we can borrow the _"mise en place"_ techniques of chef's:
![Mise En Place](mise%20en%20place.md#^9aef88)
So, the following are habits to keep the [[second brain]] tied up while we are using it:
- [Project checklists](Project%20checklists.md)
- [Periodic reviews](Periodic%20reviews.md)
- Noticing other habits:
- Noticing that an idea you have in mind could potentially be valuable and capturing it instead of thinking, “Oh, its nothing.”
- Noticing when an idea youre reading about resonates with you and taking those extra few seconds to highlight it.
- Noticing that a note could use a better title—and changing it so its easier for your future self to find it.
- Noticing you could move or link a note to another project or area where it will be more useful.
- Noticing opportunities to combine two or more Intermediate Packets into a new, larger work so you dont have to start it from scratch.
- Noticing a chance to merge similar content from different notes into the same note so its not spread around too many places.
- Noticing when an IP that you already have could help someone else solve a problem, and sharing it with them, even if its not perfect.
## Some things to keep in mind:
- **Theres no need to capture every idea**; the best ones will always come back around eventually.
- **Theres no need to clear your inbox frequently**; unlike your to-do list, theres no negative consequence if you miss a given note.
- **Theres no need to review or summarize notes on a strict timeline**; were not trying to memorize their contents or keep them top of mind.
- When organizing notes or files within PARA, its a **very forgiving decision of where to put something**, since search is so effective as a backup option.

View file

@ -0,0 +1,51 @@
---
created: 2024-02-20 19:52
updated: 2024-03-12 13:49
---
# Intermediate Packages
> [...] there is a flaw in focusing only on the final results: all the intermediate work (the notes, the drafts, the outlines, the feedback) tends to be underappreciated and undervalued. The precious attention we invested in producing that in-between work gets thrown away, never to be used again.
>
> Source: Tiago Forte, “[[Building a Second Brain]]”, p. 150
intermediate packages can receive different names depending on who you ask:
- “Modules” or “features” in software development
- “Betas” tested by start-ups
- “Sketches” in architecture
- “Pilots” for television series
- “Prototypes” made by engineers
- “Concept cars” in auto design
- “Demos” in music recording
Each of these terms is the equivalent of a “rough draft” you create as part of the process of making something new.
Some kinds of intermediate packages are:
- **Distilled notes:** Books or articles youve read and distilled so its easy to get the gist of what they contain.
- **Outtakes:** The material or ideas that didnt make it into a past project but could be used in future ones.
- **Work-in-process:** The documents, graphics, agendas, or plans you produced during past projects.
- **Final deliverables:** Concrete pieces of work youve delivered as part of past projects, which could become components of something new.
- **Documents created by others:** Knowledge assets created by people on your team, contractors or consultants, or even clients or customers, that you can reference and incorporate into your work.
These IP can be used to create others IP's or create a final product for a project.
## Benefits of working in IP's:
- Youll become **interruption-proof** because you are focusing only on one small packet at a time.
- Youll be able to make **progress in any span of time**.
- Intermediate Packets **increase the quality** of your work by allowing you to collect feedback more often.
- Eventually youll have so many IP's at your disposal that you can execute entire projects just by **assembling [previously created](Reuse%20previous%20work.md) IP's**.
## IP's Examples:
- Favorites or bookmarks saved from the web or social media
- Journal or diary entries with your personal reflections
- Highlights or underlined passages in books or articles
- Messages, photos, or videos posted on social media
- Slides or charts included in presentations
- Diagrams, mind maps, or other visuals on paper or in apps
- Recordings of meetings, interviews, talks, or presentations
- Answers to common questions you receive via email
- Written works, such as blog posts or white papers
- Documented plans and processes such as agendas, checklists, templates, or project retrospectives

View file

@ -0,0 +1,13 @@
---
created: 2024-02-10T18:26:45-03:00
modified: 2024-02-10T18:32:53-03:00
updated: 2024-03-12 13:49
---
# North Start
TODO
## 12. Questions
## Objectives

View file

@ -0,0 +1,19 @@
---
id: 9b7a4283-0523-4536-b562-4df99cd32037
created: 2024-02-02T19:52:00-03:00
updated: 2024-03-12 13:49
---
El método PARA es para un sistema de organización transversal a cualquier herramienta, ya sea física o digital.
1. Projects: Short-term efforts in your work or life that your're working on right now.
2. Areas: Long-term responsibilities you want to manage over time.
3. Resources: Topics or interest that may be useful in the future.
4. Archive: Inactive items from the other three categories.
The stuff inside each element can and should move between each category, and always should be put in the higher element because it's ordered by actionability.
This is an **organization method**, not a capture method. This mean we should not apply this when creating a note but at a later time (like a [[periodic reviews]]).
## Techniques
![Progresive Summarization](Progresive%20Summarization.md)

View file

@ -0,0 +1,57 @@
---
created: 2024-02-21 17:49
updated: 2024-03-12 13:49
---
## Periodic reviews
Periodic reviews ac as a way of _checkpoint_ in which we review how life and work is going and try to reset our minds to allow us to continue to work.
This should be forgiving, doesn't bad happens if we miss a review day.
The purpose of a review vary: depending how often is done, the scope of it increase or reduce, as well as it's certainty.
## Weekly
The purpose of a weekly review is to provide a _reset point_: empty inboxes, glow up some notes and discard what's not relevant.
This are some actions to do on a weekly review:
- **Clear my email inbox**
- Review unread emails.
- Unsubscribe from spam emails.
- Move wanted subscriptions to read-later email.
- **Check my calendar**
- Upcoming events to attend this week.
- Following weeks events that I need to prepare to.
- **Clear frequent folders**
- Downloads
- Documents
- Drive
- **Clear my notes inbox**
- Batch process them all at once, making quick, intuitive decisions about which of the PARA folders each note might be relevant to. Don't think to hard about it.
- Don't process or summarize them, this is taxing, is better to do when I work on a specific topic and I need the note.
- **Choose my tasks for the week**
- Clear the inbox of the task manager.
- Choose the tasks I want/need to do this week.
- This should be the last step, so we have the information gathered in the previous ones in consideration.
## Monthly
Since the scope of this review is a little more broad, it's recommended to review how are you going in a more general way instead of the granular approach of the weekly review.
> Its a chance to evaluate the big picture and consider more fundamental changes to your goals, priorities, and systems that you might not have the chance to think about in the busyness of the day-to-day.
>
> Tiago Forte, “[[Building a Second Brain]]”, p. 215
This are some actions to do on a monthly review:
- **Review and update my goals**
- What successes or accomplishments did I have?
- What went unexpectedly and what can I learn from it?
- **Review and update my project list**
- Archiving any completed or canceled projects
- Adding new projects
- Updating active projects to reflect how theyve changed
- **Review my areas of responsibility**
- Decide if theres anything I want to change or take action on
- **Review someday/maybe tasks**
- **Re prioritize tasks**

View file

@ -0,0 +1,18 @@
---
created: 2024-02-18 11:16
updated: 2024-03-12 13:49
---
# Progresive Summarization
técnica para destilar notas y obtener la escencia sin perder el contenido original, permitiendo poder obtener tanto contexto como necesitemos en el momento de leerla.
Para aplicar esta técnica, debemos "destacar" multiples veces, y cada vez de manera más concisza el contenido de la nota, por ejemplo:
1. Conseguir las partes importantes de un articulo (usar read-later app)
2. Marcar en negrita
3. Destacar o poner en cursiva
4. hacer un 2º resumen de un par de frases, con mis propias palabras
Es importante destacar que no es necesario aplicar todos estos pasos, ni aplicarlos de una sola vez. Esta es una tarea que requiere tiempo y esfuerzo que no siempre vale la pena invertir.
Además recordar que no hay que destacar todo, porque si todo está destacado, entonces nada lo está realmente.

File diff suppressed because one or more lines are too long

View file

@ -0,0 +1,10 @@
---
created: 2024-02-17 13:45
updated: 2024-03-12 13:49
---
Para reutilizar trabajo previo desde el _second brain_ podemos utilizar las siguientes estrategias:
- Search notes by title or content
- Manually browse the vault
- Search through [[tags]]
- [[Serendipity]] (connection between ideas & notes). for obsidian this means follow the links between notes.

View file

@ -0,0 +1,18 @@
---
created: 2024-02-21 10:54
updated: 2024-03-12 13:49
aliases:
- Motivation momentum
---
> [...] Hemingway was known for a particular writing strategy, which I call the “Hemingway Bridge.” He would always end a writing session only when he knew what came next in the story. Instead of exhausting every last idea and bit of energy, he would stop when the next plot point became clear. This meant that the next time he sat down to work on his story, he knew exactly where to start.
>
> Tiago Forte, “[[Building a Second Brain]]”, p. 186
You can think of a Hemingway Bridge as a bridge between the islands in your [Archipelago of Ideas](Archipelago%20of%20Ideas.md).
How do you create a Hemingway Bridge? Instead of burning through every last ounce of energy at the end of a work session, reserve the last few minutes to write down some of the following kinds of things in your digital notes:
- **Write down ideas for next steps:** At the end of a work session, write down what you think the next steps could be for the next one.
- **Write down the current status:** This could include your current biggest challenge, most important open question, or future roadblocks you expect.
- **Write down any details you have in mind that are likely to be forgotten once you step away:** Such as details about the characters in your story, the pitfalls of the event youre planning, or the subtle considerations of the product youre designing.
- **Write out your intention for the next work session:** Set an intention for what you plan on tackling next, the problem you intend to solve, or a certain milestone you want to reach.

View file

@ -0,0 +1,11 @@
---
created: 2024-02-21 12:59
updated: 2024-03-12 13:49
---
# Mise En Place
> [!cite]
> The preparations to cook, having the ingredients ready, such as cuts of meat, relishes, sauces, par-cooked items, spices, freshly chopped vegetables, and other components that are required for the menu and recipes ingredients measured out, washed, chopped and placed in individual bowls; and equipment such as spatulas and blenders prepared, and oven preheated.
Chefs can never afford to stop the whole kitchen just so they can clean up. They learn to keep their workspace clean and organized _in the flow of the meals they are preparing_. ^9aef88

View file

@ -0,0 +1,41 @@
---
created: 2024-02-21 19:01
updated: 2024-03-12 13:49
---
Tagging is an advance technique from ancient times where the search capabilities of modern notes app didn't exist. Because of this (and other reasons) is nearly imposible to create an universal taxonomy to catalogue all of our notes.
For this reasons we can use tags as an extensions of our mine organization and relations systems ([PARA method](PARA%20method.md) and linking).
There are three practical approaches to tagging you can use as your Second Brain grows and matures. Each one follows the principle of actionability and answers an important question about the purpose of a given note:
1. **Create personalized tags for your use cases**. (How will my notes be used?)
2. **Use tags to track the progress of notes**. (How are my notes currently being used?)
3. **Tag notes retroactively and only as needed**. (How have my notes been used?)
You can use as few or as many of these techniques as you find helpful, or use them only for specific projects or areas that demand a higher level of rigor. Each tag you create should answer a question about the past, present, or future status of a note so you always know where its been and where its going.
## Create personalized tags for your use cases
if you already know how your notes are likely to be used - such as for
citations in a paper (_Source_), as evidence in a trial (_Evidence_), or as slides in a presentation (_Slides_) - it can be helpful to **tag your notes according to those uses cases**.
Ask yourself, _“What are the most common use cases for the content I capture?”_, here are a couple common examples:
- Tagging according to the final product a note will be used in: _Presentation_,
_Essay_, _Report_, _Website_, _Project plan_, _Meeting agenda_, or _Budget_
- Tagging according to the kind of information a note contains: _Arguments_,
_Theories_, _Frameworks_, _Evidence_, _Claim_, _Counterpoint_, or _Question_
## Use tags to track the progress of notes
As your collection of knowledge expands, at some point you may feel the need to **track their progress towards the outcomes youre trying to create** in your life. You dont need to remember the status of every note.
- Tagging according to its role in a project: _Meeting notes_, _Timeline_, _Budget_, _Decision_, _Action_, _Idea_, or _Objective_
- Tagging according to the current stage of their workflow: _Planned_, _In process_, _Waiting for approval_, _Reviewed_, _Approved_, _On hold_, or _Finished_
## Tag notes retroactively and only as needed
Digital information is incredibly malleable, and it is often easier to organize your notes retroactively than to try and guess upfront all the projects, areas, and resources you might eventually need.
Tags are useful when you want a **different way of “viewing” your notes**, without having to undertake a massive reorganization of your entire system
When you apply tags with a specific use case in mind, the tags you come up with will be far more concrete and actionable.