Keeping Personal Cheat Sheets as a Software Engineer

Re:Keeping Personal Cheat Sheets as a Software Engineer by zwischenzug on Friday April 03, 2015 @12:05PM (#9316622)

I have a git repo with work notes in.

It all goes in there:

    root@osboxes:/space/git/work/notes# ls | head
    7z
    abs-guide
    algorithms
    anacron
    angularjs
    ansible
    ant
    apache2
    apt_and_dpkg

300 folders and counting...

[ Parent | on HN ]

Re:Keeping Personal Cheat Sheets as a Software Engineer by mpicker0 on Friday April 03, 2015 @02:44PM (#9317612)

I use "cheat" to help with less-used options for *NIX commands, probably similar to what you're doing. You create a separate "cheat sheet" for each command (7z, ant, etc.) and then "cheat 7z" dumps it to the console so you can cut-and-paste what you need.

https://github.com/chrisallenlane/cheat

[ Parent | on HN ]

Re:Keeping Personal Cheat Sheets as a Software Engineer by zwischenzug on Friday April 03, 2015 @02:47PM (#9317638)

So far I've relied on grep, but I like that idea and will likely implement it.

[ Parent | on HN ]

Re:Keeping Personal Cheat Sheets as a Software Engineer by pestaa on Friday April 03, 2015 @02:30PM (#9317527)

How do you manage this repository? Have auto-commits, auto-pushing, auto-anything?

[ Parent | on HN ]

Re:Keeping Personal Cheat Sheets as a Software Engineer by zwischenzug on Friday April 03, 2015 @02:46PM (#9317632)

I have automation around the downloading of pdfs that interest me and the production of man pages to pdfs. Gradually I'm developing conventions around format and so on, but it's pretty idiosyncratic, as you can imagine.

[ Parent | on HN ]