Skip to content

Comment on Ask HN: Where do you keep your Knowledge Base?

Comments

I keep a git repo of a 'commonplace book', which I prune to plain text, and keep scraps of various texts - short tutorials, poems, a password vault, and usage examples. The same repo gets loaded at home and work, and so those examples are available to each other.

One subdirectory is more magical, 'data/cheatsheets/<filenames>. If I run a bash function 'cheat $1' with the filename, it will just dump the file into a pager like the less command.

When I fizz out on how git works, I run 'cheat git' and get my own notes. I can edit it when something ends up being useless to me, and keep the most important stuff at the very bottom. Eventually it gets drilled into my head and I learn it.

This scales to one person very easily. The value is the subjectivity. With some actual editing, this would also scale to a small team of maybe 4 people.

Of course, most of the stuff in my repo would not be appropriate for sharing, but the model would extend in general.

I have an alias in git called "cheat" that will return a page of useful notes I've written (for myself).

I find it funny that I type "git cheat" where you type "cheat git".

I like your technique better, as you can easily add more technologies to the mix.

What happens if you type "cheat" with no parameter? Does it list all of the cheat sheets? (i.e. ls data/cheatsheets/*)

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.