When I am starting out on new things (like learning a new framework), or just lacking motivation, or looking to improve productivity I go back to my 'important-notes' and read them over.
This has been super helpful for me. I can give a bunch of reasons as to why it's helpful but they all boil down to this: It helps me avoid repeating mistakes, and to avoid stupidity.
In theory, it's perfect but I do not execute it well. I do not go back to them every week to filter. I do not read the 'important-notes' often. A lot of times I still make mistakes which I should not because I have clearly written about those in 'important-notes'.
Anyone else in similar situation? Do you take notes that you want to go back and read? If yes, what's your model to deal with this? Any tools that you found helpful? Any better solution to the whole idea of 'important-notes' and going back to them?
The key is to understand that organizing/filtering the relevant info is a separate task from cataloguing. I spend a little time every week doing that.
Tools -
https://workflowy.com/ - hierarchial lists, very useful! to keep track of important todos/things to remember in the week.
ultra.work/lights-generator (thats a URL) - to track habits that i want to do every day.
Thanks for sharing lights-generator. Checking it out.
http://standardnotes.org
It works out well, if not perfect. Usually, articles are not to be re-read completely, only the important parts or the gist is enough.
https://github.com/m2n037/learning_notes
Please let me know what are your thoughts regarding this. May be we will both find a better way to deal with this.
If there's certain types of learnings that I really appreciate --> I'll add it to Anki, but just a little snippet of Q/A.
Q - How should you view SSDs when scaling high traffic sites? A - "Think of SSDs as cheap memory, not expensive disk" - This was from an article from High Scalability about Reddit.
However, looks like a lot of people use it like a bookmarking tool.
and thanks for sharing your flow.
Any email I send to myself is automatically marked as read... then based on what’s in the subject line a label is automatically applied. For example, if I have an idea for a design I send an email with a subject of “Design - blah blah” and whatever text in the body. The filter I set up in Gmail looks for the word “Design” in the subject, marks it as read so I don’t get notified of a new email, and then applies the Design label. From there, I usually start an email thread on that subject line as I have more ideas.
But it should soon become overwhelming if you have a lot of content coming in. If you want to have a glance at all your saved quotes, let's say, you have to expand into each mail to read them even if they are just 2-3 lines.
I can see how this works nicely for half-baked ideas in mind. You can simple reply to the thread each time you have more points.
http://www.devontechnologies.com/products/devonthink/devonth...
https://en.wikipedia.org/wiki/Commonplace_book
In practice, this ends up being a huge markdown file (so I can store readable code) with entries prefixed by tags to make for easier searching.