![]() ![]() I have learned that, when it comes to building a knowledge base, a search is far more important and effective than super neat organization system.Īt this point, this newly established knowledge base had become a buffer for my web search. Even without complicated tags or taxonomies, all my knowledge could be easily retrieved. I could just grep a keyword because everything was in a single text file! Later I started syncing my notes to a remote Postgres database and made a web interface that could do a full-text search. Searching is far more efficient than organizingĮven though the new system did not have an elaborate organizational scheme, all my knowledge were now easily reachable. This minimalist approach helped me see that knowledge was all that mattered, and developing a sophisticated system should have never become the goal in itself. Rename stuff using `rename -n "s/ /_/g" *` - SIGHUP stands for 'signal hangup' and is sent to a process when its controlling terminal is closed bind() creates a new function - You cannot make a synchronous result out of an asynchronous operation linux: In the spirit of keeping minimal overhead, all notes had to be a single line. I wrote a simple command line program called Dnote that just kept appending stuff to a YAML file. With this in mind, I abandoned my years worth of technical notes in Evernote and decided instead to just jot down everything I learned as quickly as possible. Instead, the goal should be to retain knowledge with minimal effort. All in all, organizing knowledge should never become the goal when building a personal knowledge base. I ended up expanding an exorbitant amount of time managing tags, keywords, and hierarchy of data that I may never even retrieve. Rather, such system requires so much maintenance effort that it subverts the very thing that it promises to do–help us learn–. Organizing knowledge should never become the goalĪ super clean organization system does not actually help us retain knowledge. Yet, this system was not particularly effective. I spent a lot of time elaborating the notes and applying appropriate tags in a hope that I can make that knowledge truly mine. The notebook contained things such as gotchas and useful snippets, as well as computer science theories. Years ago, I used to keep a notebook in Evernote about coding knowledge that I thought would have been valuable to my future self. It all started with my programming notes in Evernote. In this post, I would like to share how I built it and highlight the ways that it has been particularly helpful so far. It supports categorization and search and automates spaced repetition via email. This knowledge base contains virtually everything I have learned during this period. How I Built a Personal Knowledge Base for Myself Sung Cho Storiesĭuring the past year and a half, I have been building and using my own personal knowledge base. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |