til

(TIL) Today I Learned

---

Notes:

• 24/11/23 - dev branch for .devcontainer / codespace
• 24/11/17 - upgrades ( 3.5.2 👉🏼 3.6.1 ) all good 👍🏼
  • 3.6 switched to Rust 🦀 rspack, SWC, Lightning CSS for faster builds
• 24/09/02 - upgrades ( 3.4.0 👉🏼 3.5.2 ) all good 👍🏼
• 24/07/11 - upgrades ( 3.3.2 👉🏼 3.4.0 ) all good 👍🏼
• 24/05/15 - upgrades ( 3.1.1 👉🏼 3.3.2 ) all good 👍🏼
• 24/01/28 - upgrades ( 3.0.1 -> 3.1.1 )
• 23/12/10 - modified blog layout - log @ https://davidawindham.com/til/help
• 23/11/12 - update 2.4.3 👉🏼 3.0.0 and React 17.0.2 👉🏼 18.2.0
• 23/08/18 - added private and draft notes with git controls. log @ https://davidawindham.com/til/help
• 23/05/05 - added AI page @ https://davidawindham.com/til/ai
• 23/02/11 - mv master to main / migrate to woozie
• 22/11/13 - upgraded to v.2.2.0 / added mermaid
• 12/04/2021 - added in Notes for non-technical docs / upgraded to v.2.0.0-beta.13
• 11/10/2021 - Updated the Docusaurus & NPM packages / Combined my old awesome-david repo into it for simplicity and rebuilt.

03/18/2021

Migrated this version from Gitbook because it wasn't playing nicely with Node.js v14 and it had a couple security vulnerabilities in the packages. Gitbook stop supporting the open source version likely for business reasons, so I migrated it all to https://docsify.js.org/ ... didn't do docsify because I can't generate static HTML which is what my DOM parser depends on to pull content elsewhere. Decided on using https://docusaurus.io/ instead. It required a bit of cleanup in the Markdown to do so. See: https://davidawindham.com/til/help

05/02/2017

While working on another project yesterday afternoon, I ran into set of documentation (https://docs.feathersjs.com/) 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.

About

This is a place to store some notes and documentation. It was originally built as a way to make notes on interesting things I learn based on one of my favorite sub-reddit/TIL. While installing it the first time I wrote 'Today I learned that Google will translate to and from Zulu'.

The page above in this site referring to the database and computer operating system and not the Zulu philosophy of a universal bond of sharing that connects all humanity.

I'm often searching online documentation for answers to commands, configurations, and error messages. 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 learn will be easy to record, search and edit. 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 use a static documentation instead of database because it's quicker, easier to search, under version control, and the file formats are interoperable with other software and publishing frameworks.

I'm hoping it'll help me keep my bookmarks as little less cluttered and it'll leave my desk page free for longer form essays. I'll keep the LOG in the README, add a help page, and some vi cheat sheets to get started because I'm always forgetting some of them.

Here's a map 👇🏼