Update from obsidian - thinkpad

Affected files:
.obsidian/plugins/obsidian-omnivore/data.json
.obsidian/plugins/update-time-on-edit/data.json
03. Resources/Notetaking/Habits.md
03. Resources/Notetaking/Periodic reviews.md
03. Resources/Notetaking/tags.md

03. Resources/Notetaking/Habits.md

@@ -1,6 +1,6 @@
 ---
 created: 2024-02-20 11:14
-updated: 2024-02-21 14:03
+updated: 2024-02-21 18:30
 ---
 # Habits to apply while notetaking process
 
@@ -13,13 +13,19 @@ For this, we can borrow the _"mise en place"_ techniques of chef's:
 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 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.
 
-This should be forgiving, doesn't bad happens if I miss a review day
-### Weekly
+## Some things to keep in mind:
 
-### Monthly
-
-## Noticing other habits
-
-Do this in small chunks while using the second brain
+- **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.

03. Resources/Notetaking/Periodic reviews.md

@@ -0,0 +1,57 @@
+---
+created: 2024-02-21 17:49
+updated: 2024-02-21 18:22
+---
+## 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**

03. Resources/Notetaking/tags.md

@@ -0,0 +1,41 @@
+---
+created: 2024-02-21 19:01
+updated: 2024-02-21 19:27
+---
+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.