Today I learned

windhamdavid 313a545c5d pants 2 weeks ago
db a3fb4cc3ca :yum: laravel pants 2 weeks ago
editors c3a9a94490 :elephant: 1 year ago
host 313a545c5d pants 2 weeks ago
lang 73584d72d1 :rat: 1 year ago
localhost 73584d72d1 :rat: 1 year ago
projects a3fb4cc3ca :yum: laravel pants 2 weeks ago
random 0ca41568d9 :open_file_folder: 1 year ago
saas 313a545c5d pants 2 weeks ago
server a3fb4cc3ca :yum: laravel pants 2 weeks ago
styles c72585e313 init 1 year ago
.gitignore c72585e313 init 1 year ago
.tm_properties c72585e313 init 1 year ago c72585e313 init 1 year ago a3fb4cc3ca :yum: laravel pants 2 weeks ago
book.json 887db3828b til icecast 1 month ago 561b5f8a1d emojis :crystal_ball: 1 year ago
package.json b480348aab :flushed: 1 year ago a3fb4cc3ca :yum: laravel pants 2 weeks ago



While working on another project yesterday afternoon, I ran into set of documentation ( that I spent a lot of time reading and will likely forget about sometime soon after I abandon using the library in other projects. Of course I stuffed a bookmark of the documentation into my quasi organized set of chrome bookmarks based on each project, but the fact that the documentation was hosted using Gitbook, reminded me of a practice I've seen others do.

(TIL) Today I Learned

Today I learned that Google will translate to and from Zulu. vi-2 My page is referring to the database and computer operating system and not the Zulu philosophy of a universal bond of sharing that connects all humanity. [](

One of the best sub-reddits is TIL and other organizations have published thier own TILs ( & . I figured that since I spend most of my working time with the terminal, git, and text files, a more efficient and easier method of documenting the time I spend reading other documentation would be to build my own TIL. This way the information I aquire will be easy to record, search and edit.

I'm often searching online documentation for answers to commands, configurations, and error messages. The problem is that I've found myself repeating those searches because of the breadth and depth of the amount of functions and libraries involved in development. My wife suggested I call it TIHIDI (this is how I did it) after explaining what I was working on. It makes sense to put my daily explorations into this publication in lieu of publishing them in the database of my main site because Gitbook is quicker, easier to search, and I can keep all the files in a version control repository on my local machine as well. It'll help keep me keep my bookmarks as little less cluttered and it'll leave my desk page free for longer form essays. I'm hoping this document will be of assistance. After this README, I'll write a Help page and I'll add some of my vi cheat sheets to get started.