chore: add files from master-wiki repo

_master_wiki/03. Resources/Design/Content Creators.md

@@ -0,0 +1,13 @@
+---
+created: 2024-04-14 12:43
+updated: 2024-04-15 20:56
+---
+- [Carmen Ansio](https://www.youtube.com/@CarmenAnsio)
+- Marina Aísa
+- Sarah Drasner
+- [Kevin Powell](https://www.youtube.com/@KevinPowell)
+- Miriam Suzanne
+- [Manz Dev](https://www.youtube.com/@ManzDev)
+- [Una Kravets](https://www.youtube.com/@UnaKravets/videos)
+- [Serudda](https://www.youtube.com/@serudda/videos)
+- Josh Comeau

_master_wiki/03. Resources/Design/Design.md

@@ -0,0 +1,66 @@
+---
+created: 2023-08-17 10:05
+updated: 2024-03-12 13:49
+---
+Diseñar está completamente fuera de mi zona de confort, así que estudiar como hacer, y hacer el esfuerzo de planear como diseñar la página antes de tirarme de hocico a hacerlo ha sido una experiencia bastante satisfactoria
+
+Pensar que debo realizar, que quiero comunicar y como lo quiero comunicar ha enrutado el diseño y permitiendo que sea más facil
+
+el feedback tambien ha sido satisfactorio, porque me ha hecho entender mejor que debo hacer y que no, tambien algúnos comentarios han contradecido completamente lo que yo creería que sería mejor, lo cuál ha enfocado mejor el diseño final en lo que realmente debe (y como debe) ser la página
+
+## Cómo enfatizar un elemento
+
+Para hacer que un elemento destaque del fondo, debemos ocupar _**Elevación**_,esto hará que el elemento parezca estar más cerca de la pantalla, haciendo que resalte de lo demás y atrapando la atención del usuario.
+
+La manera de lograr esto depende del tema:
+
+### Light Theme
+
+Contrastar el contorno del elemento con su entorno, para esto podemos:
+
+- Utilizar sombras, esto destaca el contorno de un elemento y su grado de elevación.
+  - sombras más pequeñas y definidas indican mayor proximidad al fondo.
+  - sombras más grandes y difuminadas indican mayor lejanía del fondo.
+- Distintos colores diferencian elementos pero no proveen su grado de elevación.
+- Opacidad muestra los contornos de los elementos y su solapamiento, pero no su grado de elevación.
+- Podemos oscurecer el fondo para destacar un elemento sobre todo lo demás, esto ofrece una gran, pero no especifica cantidad de elevación.
+
+### Dark Theme
+
+- Utilizar colores claros para denotar el grado de elevación:
+  - Utilizar colores directamente. mientras más claro sea el color, más elevado estará un componente.
+  - Aplicar un _"overlay"_ de un color claro, con distintos grados de transparencia. Mientras menos transparente más elevado estará el componente. No aplicar este esto a los colores primarios o similares.
+- _**NO**_ aplicar "light glows" en lugar de sombras oscuras para expresar elevación, porque no logran el mismo efecto.
+
+### References of common elevations
+
+| Component                                                 | Default elevation values (dp) | White overlay transparency |
+| --------------------------------------------------------- | ----------------------------- | -------------------------- |
+| Dialog                                                    | 24                            | 16%                        |
+| Modal bottom sheet Modal side sheet                       | 16                            | 15%                        |
+| Navigation drawer                                         | 16                            | 15%                        |
+| Floating action button (FAB - pressed)                    | 12                            | 14%                        |
+| Standard bottom sheet Standard side sheet                 | 8                             | 12%                        |
+| Bottom navigation bar                                     | 8                             | 12%                        |
+| Bottom app bar                                            | 8                             | 12%                        |
+| Menus and sub menus                                       | 8                             | 12%                        |
+| Card (when picked up)                                     | 8                             | 12%                        |
+| Contained button (pressed state)                          | 8                             | 12%                        |
+| Floating action button (FAB - resting elevation) Snackbar | 6                             | 11%                        |
+| Top app bar (scrolled state)                              | 4                             | 9%                         |
+| Top app bar (resting elevation)                           | 0 or 4                        | 0% - 9%                    |
+| Refresh indicator Search bar (scrolled state)             | 3                             | 8%                         |
+| Contained button (resting elevation)                      | 2                             | 7%                         |
+| Search bar (resting elevation)                            | 1                             | 5%                         |
+| Card (resting elevation)                                  | 1                             | 5%                         |
+| Switch                                                    | 1                             | 5%                         |
+| Text button                                               | 0                             | 0%                         |
+| Standard side sheet                                       | 0                             | 0%                         |
+
+Reference:
+
+- [Material Design - UI](https://m2.material.io/design/environment/elevation.html)
+- [Material Design - Dark Theme](https://m2.material.io/design/color/dark-theme.html)
+
+
+![Layouts](Layouts.md)

_master_wiki/03. Resources/Design/Layouts.md

@@ -0,0 +1,6 @@
+---
+created: 2024-02-29 18:36
+updated: 2024-03-12 13:49
+---
+## Layouts
+- [How to Properly Layout A Website (For Beginners)](https://www.youtube.com/watch?v=3C_22eBWpjg&t=604s)

_master_wiki/03. Resources/Design/Story Telling.md

@@ -0,0 +1,147 @@
+---
+created: 2024-04-03 12:11
+updated: 2024-04-03 13:52
+---
+
+# Story Telling
+
+## El Arco Narrativo
+
+- Ir de un punto álgido a otro bajo y volver a subir es lo que have que una historia de la satisfactoria sensación de estar completa
+- Una historia comienza con un _"llamado a la acción"_, el verbo mueve al sujeto.
+
+## El Viaje Del Héroe
+
+Se puede utilizar el patrón del _"viaje del héroe"_ en el diseño para guiar a los usuarios:
+
+- Un incidente iniciante o una problemática que incita al "héroe" a moverse de donde está
+- El "llamado a la aventura" es donde se incita al usuario a algo
+- El "cruce del umbral", en donde el usuario entra en el otro sector (posiblemente hostil) en donde tendrá que pasar la "prueba de fuego"
+- El camio de vuelta, donde regresamos al origen pero co algo nuevo ("regreso con el elixir")
+
+## Story Boards
+
+Los story boards son herramientas para planificar la acción transformadora de una historia.
+
+Contar una historia en 6 fotogramas es una buena manera de contar los elementos esenciales de la forma narrativa
+
+## Ingredientes De Una Historia
+
+- **Arco**: la acción tiene un principio, un nudo y un final.
+- **Cambio**: la acción transforma a un personaje o una situación.
+- **Tema**: la acción se construye a partir de detalles concretos y relevantes.
+- **Plausibilidad**: la acción es verosímil y sigue sus propias reglas.
+
+## Regla De 3
+
+Contar una historia en 3 pasos es una herramienta poderosa:
+
+- 3 pasos da la sensación de facilidad y rapidez, aunque estos 3 pasos engloben más en secreto, agrupar tareas suele estar bien mientras no genere confusión
+- Si se utilize de modo que el ultimo elemento es inesperado, puede sorprender y generar una sensación de satisfacción
+- Ayuda a la memorización de elementos clave, sobre todo combinado con el item anterior
+
+Esta regla se puede extender a 4 pasos, perdiendo cierta efectividad. Más de
+4 pasos no suele set rentable, ya que da una sensación de set demasiado largo y "latero"
+
+## Conexiones Forzadas
+
+Aplicar conceptos e ideas, que en un principio pueden parecer contrarias o inconexas puede llevar a nuevas ideas y diseños interesantes, se puede emplear un concepto (Extraterrestre, colosal, vulgar, zoologico, etc) a un elemento a diseñar y ver que ocurre.
+
+## Emoción
+
+El diseño destinado a susitar emociones require pensar en como los usuarios anticiparán una experiencia y cómo la recordarán después.
+
+>[!quote]
+>  "Las emociones son una palanca para la acción."
+>
+>  "Los diseñadores necesitan adoptar estrategias para acceder a los contextos emocionales de los productos que tienen que diseñar, pensando en la gente que los usará."
+
+![](IMG_20230722_120651_229.jpg)
+
+![](IMG_20230722_121658_512.jpg)
+
+## Economía De la Experiencia
+
+Durante una experiencia, los usuarios generan significados y asociaciones que adquieren una mayor importancia que la del propio acontecimiento
+
+Una experiencia es algo más de lo que se consume en el memento. Integra al consumidor en una representación teatral, creando un recuerdo perdurable y un lazo emocional.
+
+![](IMG_20230722_123447_567.jpg)
+
+Las experiencias se crean cuando los diseñadores deplazan el **foco** de los objetos a las acciones:
+
+> [!info]
+> Esto no necesariamente significa que el usuario realice algo, sino mover el principal elemento a una acción:
+> - Auto -> conducir
+> - Restaurant -> Cenar
+> - Universidad -> Aprender
+
+## El Viaje Emocional
+
+Si una trama consiste en más de una series de sucesos que conforman una historia, un viaje emocional consiste en los sentimientos que esos sucesos despiertan
+
+![](Pasted%20image%2020240403125253.png)
+
+![](IMG_20230722_125137_501.jpg)
+
+La forma en que concluye una experiencia afecta el juicio que los usuarios emitirán sobre el acontecimiento completo.
+
+Prestar especial atención a la forma en la que concluyen las acciones, ofreciendo un extra de carga emocional para recompensar a los usuarios por su tiempo y esfuerzo.
+
+## Cocreación
+
+Los diseñadores trabajan junto a los usuarios, los cuales son considerados "un experto en el tema tratado".
+
+## Técnicas Útiles
+
+### Mapa De Palabras
+
+Cada participante escribe un tema en el centro de una hoja, mediante un proceso de libre asociación, los participantes dibujan o escriben conceptos asociados para crear nodos de ideas
+
+![](Pasted%20image%2020240403133913.png)
+
+### Fuerzas Positivas Y Negativas
+
+Crear una matriz de conceptos + y -
+
+|                                        | Pros                                   | Cons                                                |
+| -------------------------------------- | -------------------------------------- | --------------------------------------------------- |
+| Cómo hacer que más gente tome la micro | - ahorrar dinero<br>- Leer en el viaje | - Tiempo de viaje<br>- No hay lugar para bicicletas |
+
+> [!question]
+> Tendrá que ver con [[FODA]]??
+
+### Asociación
+
+Se le asignan emociones o personalidad a una idea
+
+![](Pasted%20image%2020240403134732.png)
+
+### Estudio De Personaje
+
+Crear una planilla para un producto como si fuera una persona:
+
+- Que edad tiene?
+- En que trabaja?
+- Cómo vive?
+- Cómo viste?
+- Donde pasará sus vacaciones?
+
+Se puede partir tratando de imaginar al usuario que va dirigido el producto y simular su estilo de vida
+
+Ej:
+
+Perfile #1, Altavoz inalámbrico:
+
+- Edad: 25
+- Ocupación: Programador
+- Vivienda: Depto. urbano
+- Transporte: Bicicleta
+- Ropa: Jeans y vintage
+
+## Color Y Las Emociones
+
+## References
+
+- El diseño como STORYTELLING - Ellen Lupton
+- [Design notes on pdf](Design_Cheatsheet.pdf)

_master_wiki/03. Resources/Development/CSS and Component Libraries.md

@@ -0,0 +1,8 @@
+---
+created: 2024-02-28 13:18
+updated: 2024-03-12 13:49
+---
+
+| Library                             | Description                                                                                                        |
+| ----------------------------------- | ------------------------------------------------------------------------------------------------------------------ |
+| [shadcn/ui](https://ui.shadcn.com/) | Beautifully designed components that you can copy and paste into your apps. Accessible. Customizable. Open Source. |

_master_wiki/03. Resources/Development/Devtools.md

@@ -0,0 +1,30 @@
+---
+created: 2024-04-15 20:56
+updated: 2024-04-15 20:56
+---
+# Devtools
+
+List of tools to solve common problems
+
+## Tasks Runners
+
+- [Overseer](https://github.com/stevearc/overseer.nvim): nvim task management
+
+## Debugging
+
+- [debugprint.nvim](https://github.com/andrewferrier/debugprint.nvim): manage print statements with useful information inside neovim
+
+## Nvim Tools
+
+### Focus Mode
+
+- [Zen mode](https://github.com/folke/zen-mode.nvim): focus on the current portion of a file only
+
+### Codebase Navigation
+
+- Telescope
+- [Graple](https://github.com/stevearc/overseer.nvim), bookmarks files to instant navigation in 1 key chord
+
+### File Navigation
+
+- [flash.nvim](https://github.com/folke/flash.nvim): jump to any place, enhances search, `f`,`F`,`t`,`T`, motions

_master_wiki/03. Resources/Development/Docker.md

@@ -0,0 +1,17 @@
+# Docker
+
+## Publish Container Images
+
+To easily create multi-arch containers and publish them to a registry, use this snipped (note you need to be logged in the registry):
+
+Create builder container:
+```bash
+docker buildx create --name mybuilder --use --bootstrap
+```
+
+Build and publish image:
+```bash
+docker buildx build --push \
+--platform linux/amd64,linux/arm64 \
+--tag ghcr.io/<name-space>/<image>:latest .
+```

_master_wiki/03. Resources/Development/Feature shipment checklist.md

@@ -0,0 +1,9 @@
+---
+created: 2024-02-20 11:39
+updated: 2024-03-12 13:49
+---
+When a feature or module is shipt, I need to asure the following things before submiting:
+
+- Clean & readable code
+- Linter without errors
+- Design is as close as posible to the proposal

_master_wiki/03. Resources/Development/Fix messy commits.md

@@ -0,0 +1,25 @@
+---
+created: 2024-02-20 11:27
+updated: 2024-03-12 13:49
+tags:
+  - dev-tools
+---
+# Fix messy commits
+
+Ya que estas opciones sobre escriben el historial de git, solo deben aplicarse en local y no commits publicados a un remote. 
+
+Como alternativa se puede intentar actualizar el historial remoto siempre y cuando el historial sea igual al local (osea, nosotros fuimos los últimos en actualizarlo y nadie ha hecho nada más). Para esto utilizamos `git push --force-with-lease`.
+
+## Last commit
+
+Si solo necesitamos agregar un cambio pequeño al ultimo commit (typo o correr el formatter), podemos aplicarlo con `git commit --ammend`, se puede sobre escribir el mensaje con `-m`.
+
+## Mutiple commits
+
+Se pueden arreglar el historial de commits con un `git rebase -i [since commit or branch]` y utilizar las estrategias de pick, squash, reword y drop.
+
+En caso de que sepamos que haremos un commit que luego no necesitaremos, podemos hacer:
+- `git commit --fixup [commit hash]` -> descarta el commit message de este commit y mantiene el del commit de referencia
+- `git commit --squash [commit hash]` -> git juntará los mensajes de todos los commits a hacer squash y el commit de referencia.
+
+Finalmente podemos hacer `git rebase -i --autosquash` y git eligirá las opciones necesarias a tomar en vez de tener que hacerlo de manera manual.

_master_wiki/03. Resources/Development/Git/Git.md

@@ -0,0 +1,14 @@
+---
+created: 2024-02-13 22:36
+updated: 2024-03-12 13:49
+tags:
+  - dev-tools
+---
+
+![Git Merge vs Rebase vs Squash ¿Qué estrategia debemos elegir](2023-11-04%20-%20Git%20Merge%20vs%20Rebase%20vs%20Squash%20¿Qué%20estrategia%20debemos%20elegir-.md#notes)
+
+![Utilizar `git bisect`](Search%20for%20a%20bug.md#Utilizar%20`git%20bisect`)
+
+![Fix messy commits](Fix%20messy%20commits.md)
+
+![Revert old changes in a codebase](Revert%20old%20changes%20in%20a%20codebase.md)

_master_wiki/03. Resources/Development/Git/So You Think You Know Git Part 2 - DevWorld 2024.md

@@ -0,0 +1,65 @@
+# So You Think You Know Git Part 2 - DevWorld 2024
+
+## Switch and Restore
+
+Wrapper around the `checkout` command to make more sense. You can do:
+
+- `git switch branch` instead of `git checkout bracnh`
+- `git restore file.txt` instead of `git checkout file.txt`
+
+![](Pasted%20image%2020240417084933.png)
+
+## Git Hooks
+
+![](Pasted%20image%2020240417084959.png)
+
+useful ones:
+
+![](Pasted%20image%2020240417085036.png)
+
+uses:
+
+- Commit message formatting
+- package install
+- update ctags
+- submodule status
+- tabs or spaces
+- linting
+- large files
+- test passes
+
+Helpers (installable external tools):
+
+- pre-commits
+- husky
+
+## Attributes
+
+run files through intermediates and diff that:
+
+```bash
+echo '*.png diff=lexif' >> .gitattributes
+git config diff.exif.textconv exiftool
+``` 
+
+## Fixup Commits
+
+`git commit --fixup=<commit>`
+`git rebase --autosquash`
+
+## Rebasing Stacks
+
+move dangling branches reference when doing a rebase
+
+`git rebase --update-refs`
+
+## Scaling Git
+
+top level command `scalar`, it's only used to clone huge repositories.
+
+## Worktrees
+
+- working on more than one branch at a time
+- provide a new working directory to each branch
+
+![](https://www.youtube.com/watch?v=Md44rcw13k4)

_master_wiki/03. Resources/Development/Iframes.md

@@ -0,0 +1,24 @@
+---
+created: 2024-02-20 11:43
+updated: 2024-03-12 13:49
+---
+
+## How to make an Iframe 100% it's parent width while maintaining the aspect ratio
+
+In this example, we need to wrap the iframe in a container class and provide the following styles:
+
+```css
+.container {
+    position: relative;
+    width: 100%;
+    height: 0;
+    padding-bottom: 56.25%;
+}
+iframe {
+    position: absolute;
+    top: 0;
+    left: 0;
+    width: 100%;
+    height: 100%;
+}
+```

_master_wiki/03. Resources/Development/Revert old changes in a codebase.md

@@ -0,0 +1,15 @@
+---
+created: 2024-02-20 11:34
+updated: 2024-03-12 13:49
+tags:
+  - dev-tools
+---
+## Revertir cambios
+
+Si necesitamos _"deshacer"_ los cambios introducidos en uno o multiples commits, podemos utilizar `git revert --no-edit older_commit_hashˆ..newer_commit_hash`, donde:
+
+- git realizará un nuevo commit con los cambios contrarios por cada commit en el rango
+- utilizar `ˆ` en el `old_commit_hash` incluirá ese commit en la reversión de cambios, si no se agrega se empezará a revertir de un commit más adelante.
+- `--no-edit` es utilizado para que git no nos pregunte por el message de cada nuevo commit
+- primero debe ser el commit más antiguo, porque git creará nuevos commits en orden provisto y de hacerlo al revés aparecerán conflictos
+- si solo se quiere revertir un commit, se puede especificar solo ese hash

_master_wiki/03. Resources/Development/Search for a bug.md

@@ -0,0 +1,9 @@
+---
+created: 2024-02-20 11:35
+updated: 2024-03-12 13:49
+---
+# Buscar cuando un bug se introdujo
+
+## Utilizar `git bisect`
+
+`git bisect` hará un _"binary search"_ entre 2 commits, dejandonos señalar si este commit es _"bueno"_ (no tiene el bug) o _"malo"_ (tiene el bug), permitiendo encontrar el commit que introdujo el bug y facilitar encontrar la causa de este.

_master_wiki/03. Resources/Notetaking/12. Questions.md

@@ -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

_master_wiki/03. Resources/Notetaking/Archipelago of Ideas.md

@@ -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.

_master_wiki/03. Resources/Notetaking/Dial down the scope.md

@@ -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 don’t 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 you’d like to make a short film, start with a YouTube video, or if that’s too intimidating, a livestream. If it’s 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.

_master_wiki/03. Resources/Notetaking/Habits.md

@@ -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, it’s nothing.”
+	- Noticing when an idea you’re 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 it’s 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 don’t have to start it from scratch.
+	- Noticing a chance to merge similar content from different notes into the same note so it’s 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 it’s not perfect.
+
+## Some things to keep in mind:
+
+- **There’s no need to capture every idea**; the best ones will always come back around eventually.
+- **There’s no need to clear your inbox frequently**; unlike your to-do list, there’s no negative consequence if you miss a given note.
+- **There’s no need to review or summarize notes on a strict timeline**; we’re not trying to memorize their contents or keep them top of mind.
+- When organizing notes or files within PARA, it’s a **very forgiving decision of where to put something**, since search is so effective as a backup option.

_master_wiki/03. Resources/Notetaking/Intermediate Packages.md

@@ -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 you’ve read and distilled so it’s easy to get the gist of what they contain.
+- **Outtakes:** The material or ideas that didn’t 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 you’ve 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:
+
+- You’ll become **interruption-proof** because you are focusing only on one small packet at a time.
+- You’ll 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 you’ll 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

_master_wiki/03. Resources/Notetaking/North Start.md

@@ -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

_master_wiki/03. Resources/Notetaking/PARA method.md

@@ -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)

_master_wiki/03. Resources/Notetaking/Periodic reviews.md

@@ -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.
+
+> It’s 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 they’ve changed
+- **Review my areas of responsibility**
+	- Decide if there’s anything I want to change or take action on
+- **Review someday/maybe tasks**
+- **Re prioritize tasks**

_master_wiki/03. Resources/Notetaking/Progresive Summarization.md

@@ -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.

_master_wiki/03. Resources/Notetaking/Reuse previous work.md

@@ -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.

_master_wiki/03. Resources/Notetaking/The Hemingway Bridge.md

@@ -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 you’re planning, or the subtle considerations of the product you’re 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.

_master_wiki/03. Resources/Notetaking/mise en place.md

@@ -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

_master_wiki/03. Resources/Notetaking/tags.md

@@ -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 it’s been and where it’s 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 you’re trying to create** in your life. You don’t 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.

_master_wiki/03. Resources/Productivity/Time Blocking.md

@@ -0,0 +1,27 @@
+---
+created: 2024-03-27 23:08
+updated: 2024-03-27 23:29
+---
+Time blocking is a time management method that asks you to **divide your day into blocks of time**. Each block is dedicated to accomplishing a **specific task or group of tasks**, and only those specific tasks.
+
+With days that are time blocked in advance, you **won’t have to constantly make choices about what to focus on**. 
+
+## types of time Block
+
+### Time Blocking or Calendar Block
+
+Set a timeframe to work on a specific tasks, this doesn't mean you need to finish it then, just that you'll work in this timeframe on this task and this task alone.
+
+## Tasks batching
+
+Group a bunch of small and similar tasks and allocate a timeframe to work on them, this is usefull to reduce the context switching.
+
+### Day theming
+
+task batching at a bigger scale, dedicate a whole day to a specific area.
+
+### Time boxing
+
+Is the same as time blocking, but this time we'll have to end the task withing the timeframe. This is to force you to produce something finished, ether by being really efficient or by reducing the scope of the tasks to something archivable. the idea is not to produce a mediocre product, but to **finish stuff**
+
+This will align with [The cult of done](The%20cult%20of%20done.md) idea and that 80% completion of the task will use the same time/effort as the reminding 20%.