Keeping Personal Cheat Sheets as a Software Engineer

#1

Post by f1gm3nt » Fri, Apr 03, 2015, 1:57 PM UTC

Keeping Personal Cheat Sheets as a Software Engineer
joshuaestes.me

Re: Keeping Personal Cheat Sheets as a Software Engineer

#2

Post by japhyr » Fri, Apr 03, 2015, 3:14 PM UTC

If you like this idea, you might want to check out Cheatography - it's a tool for creating stylish cheat sheets. I used it a little when it was first announced, but haven't kept up with it. It's a great idea, and the developer was really friendly when I was checking it out.

http://www.cheatography.com/

Re: Keeping Personal Cheat Sheets as a Software Engineer

#3

Post by dikaiosune » Fri, Apr 03, 2015, 3:54 PM UTC

I've tried this several times, but I always find that by the time I've been stumped by something enough times to write it down, I'm on the verge of having it learned anyway. So, my cheat sheets just become random bits of paper full of stuff I already know, and I start new ones. Rinse and repeat. It's a nifty trick but I don't think there's any substitute for good ol' repetition and understanding.

Re: Keeping Personal Cheat Sheets as a Software Engineer

#4

Post by JoeAltmaier » Fri, Apr 03, 2015, 3:55 PM UTC

Hm. How about a cheat-web-link? This stuff's gotta already be online, neatly summarized.

Re: Keeping Personal Cheat Sheets as a Software Engineer

#5

Post by Excluse » Fri, Apr 03, 2015, 3:57 PM UTC

http://www.mediaatelier.com/CheatSheet/

Hold 'command' key to see all shortcuts for current application.

Re: Keeping Personal Cheat Sheets as a Software Engineer

#6

Post by zwischenzug » Fri, Apr 03, 2015, 4:05 PM UTC

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...

Re: Keeping Personal Cheat Sheets as a Software Engineer

#7

Post by zwischenzug » Fri, Apr 03, 2015, 4:05 PM UTC

dikaiosune wrote: post #3

I've tried this several times, but I always find that by the time I've been stumped by something enough times to write it down, I'm on the verge of having it learned anyway. So, my cheat sheets just become random bits of paper full of stuff I already know, and I start new ones. Rinse and repeat. It's a nifty trick but I don't think there's any substitute for good ol' repetition and understanding.

Ha! When you're old enough you'll forget what you've forgotten you've forgotten.

Re: Keeping Personal Cheat Sheets as a Software Engineer

#8

Post by artmageddon » Fri, Apr 03, 2015, 4:11 PM UTC

dikaiosune wrote: post #3

I've tried this several times, but I always find that by the time I've been stumped by something enough times to write it down, I'm on the verge of having it learned anyway. So, my cheat sheets just become random bits of paper full of stuff I already know, and I start new ones. Rinse and repeat. It's a nifty trick but I don't think there's any substitute for good ol' repetition and understanding.

Right, but while you might know how to do it, the person next to you may not. I write stuff down because it might be an issue that I encounter once every 6 months and I hate to have to relearn it, but also someone might run into the same issue, and I can expend less brain power/time to help someone else learn it.

Re: Keeping Personal Cheat Sheets as a Software Engineer

#9

Post by rogerniner » Fri, Apr 03, 2015, 4:36 PM UTC

I keep appending to a file in my home directory. I've aliased it too so that I can access it quickly. Every ~month I email it to myself or back it up elsewhere.

$ alias ed

alias ed='$EDITOR ~/.diary"

The file looks something like this:

# 4/3/2015

Command Comments

-------------------------------------------

M-l # Emacs, lowercase next word

Re: Keeping Personal Cheat Sheets as a Software Engineer

#10

Post by 2mur » Fri, Apr 03, 2015, 4:41 PM UTC

My vim cheatsheet lives in my dotfiles repo. Always gets cloned into a fresh system.