content: update be-kind-to-your-future-self.md

src/content/blog/be-kind-to-your-future-self.md

@@ -21,17 +21,17 @@ So, here's where taking good notes becomes a superhero move for developers.
 
 ## Brain is a processor, not a warehouse
 
-How many times have you thought you'd remember that clever solution or tricky code? Or maybe you had a meeting where you figure out important solution you will for sure remember (spoiler alert: you don’t).
+How many times have you thought you'd remember that clever solution or tricky code? Or maybe you had a meeting where you figured out an important solution you will for sure remember (spoiler alert: you don’t).
 
-Our brains not good at storing "raw" information (without understing and connect them). Relying only on memory is like building a castle on sand. It might look good for a bit, but it won't last.
+Our brains are not good at storing "raw" information (without understanding and connecting them). Relying only on memory is like building a castle on sand. It might look good for a bit, but it won't last.
 
 **The only option is to externalize the ideas.**
 
-When you close your thought in a note it becomes...object and since now you can with it.
+When you close your thought in a note it becomes...object and now you can with it.
 
-You can edit, split, and merge with other ideas, add properties, and restructure. It's easy to back and reuse that object. Upon on these little objects you can build next one and create whole system of knowledge.
+You can edit, split, and merge with other ideas, add properties, and restructure. It's easy to back and reuse that object. Upon these little objects, you can build the next one and create a whole system of knowledge.
 
-Yup, it's analogy for building system from function -> classes -> modules. Pretty cool, isn't it?
+Yup, it's an analogy for building a system from function -> classes -> modules. Pretty cool, isn't it?
 
 ![Evergreen notes as object by @kepano](@assets/images/be-kind-to-your-future-self/01.png)
 
@@ -44,9 +44,9 @@ Think about notes like a message for your future self. Ask yourself:
 - **”Under what contexts I’d like to find it in the future?”** Would be related it to feature A, project B? Is it frontend, or backend stuff?
 - “In a few weeks, or a few months, or even a year or more, when I come back to this note, what do I know now that will be useful then?” (@tfthacker)
 
-Ask for following questions? Great! 👏
+Ask for the following questions? Great! 👏
 
-You should find several context for each note. It can be related with person, meeting, feature, technology. Yet, how to put all these contexts into note, how connect them!? Use a graph.
+You should find several contexts for each note. It can be related to a person, meeting, feature, or technology. Yet, how to put all these contexts into the note, how to connect them!? Use a graph.
 
 ## Build network, not archive
 
@@ -66,6 +66,12 @@ How can I reach the note in my system?
 - Start from broader topics like `Graph`, `Data Structure` and go down
 - Start from related topics like `Kruksal Algorithm`, `Spanning Tree`
 
-Thanks to graph **I don’t have to remember exactly location of this note** and can find it more easily and faster by related contexts.
+
+
+https://github.com/paczkow/paczkow.dev/assets/16765560/38979b8b-140d-41f8-9b6f-a408072785aa
+
+
+
+Thanks to graph **I don’t have to remember the exact location of this note** and can find it more easily and faster by related contexts.
 
 Try it and I’m sure your future self will be more productive and certainly will be grateful as well as the rest of the team.