Accountability & Continuity

"If I have to look it up twice, I'm writing it down." 

This is what I told myself after repeatedly looking up how to do things that I didn't know. I wanted to create a personal continuity book based on helpful commands, and use it as a way to hold myself accountable to learn and expand my knowledge. 

It started out primarily with bash commands I was using for incident response, things that I was astonished folks could remember without referencing (like specific `sed` and `awk` commands). It quickly became an all-encompassing list of various other commands in other languages, such as Python, Go, SQL, and more.  

Not only do I continue to add to this list, but I also use it often, and it's been very helpful during my security and development work: https://github.com/hackersifu/command_cheat_sheet 

What do you use for your own continuity book? I'm curious to hear any ideas or feedback in the comments!