Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Ask HN: Can I see your cheatsheet?

news.ycombinator.com

Post reply on HN
Print view View original

161–170 of 173 posts

Re: Ask HN: Can I see your cheatsheet?

#161

Post by yourcousinbilly »

wainage wrote: post #142
yourcousinbilly wrote: post #141

I have a massive Cheatsheet for most languages and many packages- https://github.com/jsfuentes/Code-Cheatsheet Also hosted on gitbooks: https://openai.gitbook.io/code-cheatsheets/

Very nice. Found your first Mac shortcut immediately helpful. I'm assuming you commit an Obsidian vault directly. Do you sweep for secrets before you commit? Your layout resembles my own, but I often dump keys / secrets into my vault "temporarily" and forget about removing them later.

Thanks! I built this from the beginning to be public, so have got into the habit to both copy and paste whenever I learn something new and obfuscate secrets.

I have had the current problem of its so massive that finding the specific sheet can take too long. I tried Obsidian, but still look for great fast search

Re: Ask HN: Can I see your cheatsheet?

#162

Post by asicsp »

parentheses wrote: post #156
asicsp wrote: post #60

I use my ebooks for reference: * GNU grep and ripgrep ( https://learnbyexample.github.io/learn_gnugrep_ripgrep/ ) * GNU sed ( https://learnbyexample.github.io/learn_gnused/ ) * GNU awk ( https://learnbyexample.github.io/learn_gnuawk/ ) * Ruby one-liners cookbook ( https://learnbyexample.github.io/learn_ruby_oneliners/ ) * Perl one-liners cookbook ( https://learnbyexample.github.io/learn_perl_oneliners/ ) * Command li…

Great work! Seriously cool e-books! (edit: reading this i sound like a jerk. wasn’t trying to be one.) However, these are books not cheat sheets. Cheat sheets are about glance ability and one page ness.

That's a fair point, something like `tldr` and `cheat.sh` mentioned elsewhere in this thread.

Re: Ask HN: Can I see your cheatsheet?

#163

Post by asicsp »

jjice wrote: post #146
asicsp wrote: post #60

I use my ebooks for reference: * GNU grep and ripgrep ( https://learnbyexample.github.io/learn_gnugrep_ripgrep/ ) * GNU sed ( https://learnbyexample.github.io/learn_gnused/ ) * GNU awk ( https://learnbyexample.github.io/learn_gnuawk/ ) * Ruby one-liners cookbook ( https://learnbyexample.github.io/learn_ruby_oneliners/ ) * Perl one-liners cookbook ( https://learnbyexample.github.io/learn_perl_oneliners/ ) * Command li…

I see you sell your books as ebooks (awesome BTW), but there's no print option. I've been looking into publishing methods for a book I've been writing, and having a print copy is very appealing (I'm a big physical book fan, personally). I see a lot of modern software books are digital only. Is this due to the margins on print being much lower than digital? Print on demand is a really neat concept to me, but seems to…

I haven't really looked into print on demand. I started with ebooks since that seemed the easiest option for me. And it is easy for readers to get updated versions.

My books are around 100 pages and I've seen a few readers mentioning that they just print it themselves.

Re: Ask HN: Can I see your cheatsheet?

#164

Post by mosselman »

justusthane wrote: post #152
mosselman wrote: post #23

http://cht.sh/ - I use this a lot. It outputs a short summary of common commands for many cli tools. You can curl to it https://cht.sh/grep for example or install their cli client

This is awesome! Thank you! I am so frequently visiting https://tmuxcheatsheet.com/ , and it's not even that great of a cheat sheet.

Glad you found it useful. It has become one of the things I install when I setup a machine.

Being able to use curl as a client as well is so powerful as well. Whenever you are using ssh on some vps you can still get cheatsheets for all your commands.

Re: Ask HN: Can I see your cheatsheet?

#166

Post by xupybd »

MonkeyClub wrote: post #90
valbaca wrote: post #12

Earlier quoted context omitted.

tldr is one of the best things to happen to the command line

I'm probably missing something here, but it seems to me that it's just a summary of the command plus a few examples? I usually just man the command and / my way either to the Examples section, or search for whatever other question I may have. But I'm on OpenBSD, where man pages are worth the time you spend reading them. Other than that, although I always intend to add useful stuff to my ~/txt/scratch, in the end it's…

Man pages are worth reading. Once you have a good handle on the command TLDR is great. It gives you you just enough to jog your memory.

Searching history or keeping your own notes work but this is easier for me. Everyone finds a work flow they like. It might not be the tool for you.

Re: Ask HN: Can I see your cheatsheet?

#167

Post by jcubic »

mosselman wrote: post #23

http://cht.sh/ - I use this a lot. It outputs a short summary of common commands for many cli tools. You can curl to it https://cht.sh/grep for example or install their cli client

I completely forget that I have this function in my dot files:

doc () { curl "https://cheat.sh/$1" | less }

Re: Ask HN: Can I see your cheatsheet?

#168

Post by rsanek »

rjh29 wrote: post #35

Try using flashcards (Anki) to remember shortcuts if you haven't yet. Just like with learning a foreign language, it's a quick way to get "action -> shortcut" mappings into your brain permanently for recall at any time, rather than relying on a cheatsheet.

If you're not already using Anki, https://www.shortcutfoo.com/ might be the simplest way to go about this.
Post reply on HN