48 comments

[ 253 ms ] story [ 958 ms ] thread
The regexp cheat sheet is missing the most important part, which is the characters you need to escape.
(comment deleted)
The R cheat sheet also looks incomplete. Is this a work in progress?
This is good cheat sheets, but can we have PDF downloads for it ? Also PhalconPHP would be a great addition :)
Impressive until you get to C++ and it turns into a random hodgepodge of 404s or really weak references (no pun intended).

Also, this same cheat sheet has been shared on HN 14 times now. Not a bad thing but interesting none the less.

>>Also, this same cheat sheet has been shared on HN 14 times now. Not a bad thing but interesting none the less.

It still gets to the front page most of the time.

Scala's says

“Every value is an object & every operation is a message send.”

I've never heard that coming from Scala.

A lot of the sheets are incomplete. The guitar sheet could use a basic chords sheet, that would be handy when you need to take a break from the computer.
I also like https://learnxinyminutes.com for when I need to understand some code in an unfamiliar language. That site also accepts contributions from anyone via pull request on GitHub.
Learn X in Y Minutes is also my go to site for dealing with code in an unfamiliar language. It's managed to get me through learning Ruby and Coffeescript on the job, as well as learning PHP for university.

It's a pity that nobody has done one for SQL yet, I would've thought it would be in high demand.

Also helped me a lot when I was learning Javascript from Codecademy. It introduced me to Eloquent Javascript book and Mozilla Developers Network.
It's good to quickly grasp basic syntax so you can read code in unfamiliar language. However, I don't think that it's a good resource to properly learn language.

You will often miss learning the philosophy of the language (the $language_name way of doing it), the different way of thinking about the problems that the language provides and similar details, which are often not necessary to read a snippet of code, but you want to understand it in order to properly learn the language and make the most of it.

SQL is a good example of it. It might be trivial to explain the syntax of most common SQL queries, but thinking in relations and tables is not natural to most people so there's not much you can do with basic syntax.

When would someone actually use a cheat sheet instead of google?
When one is exploring domain specific command sets.
Usually when you think you can find some new treasures in there fast. I use an API cheat sheet all the time.

Also when the topic at hand isn't very google-able and the cheat sheet is the next most efficient choice.

But a lot of the time cheat sheets get useless fast.

To find something specific you need? probably not. Google's probably still the easiest.

To go "I want to refresh myself on X's commands and syntax", read over a short cheat sheet? Maybe

Working in a fully offline environment, I have git repository with only documentation for everything I may need. In this situation, a cheat sheet or a searchable doc can save my day.
I think both are useful depending on the situation. Maybe a better question is why I'd want a potentially outdated list of cheat sheets instead google. I bookmarked it anyway.
Back in the day when I actually had a desk and walls on which to pin things, I printed out and stuck cheat sheets from the 4 languages in effective use in my context: SAS, R, python and C.

The lag/effort was/is far less than google if the info is right there, and I personally found I kept having brain farts where I'd temporarily forget what language the thought I was having was actually in, and could quickly touch base again by referencing the cheat sheet without bringing up the (often distracting) web browser...

If you like this sort of thing (and have a Mac), you'll probably enjoy Dash. It's particularly great to load up on anything you feel you might need before heading towards flaky international internet access for a while.

https://kapeli.com/dash

DevDocs is a great alternative for those of us that don't use Macs. Works fully in the browser, even with no network, which is kinda cool.

http://devdocs.io/offline

https://zealdocs.org/ was the one I tried, but the main problem is that it didn't support zip/tar files and Windows (explorer.exe mainly) gets very slow when there are >10 000 files in one path.
Wow it got really lots of new stuff since I last checked! The offline option sounds cool if you're working on a laptop while commuting etc.
DevDocs is great, highly recommended!
Should fix the CSS so it looks good when printed.
overapi.com can be useful if you want to discover something... but for daily use I prefer devdocs.io
The Java page is basically a list of links to tutorialspoint.com, which seems like an odd choice.
Would be sweet if you could customize the options in your printed sheets. Example: I know how to preform basic git operations, but sometimes I need a reminder of how to push a local branch to a remote with a different branch name.
A mercurial cheat-sheet would be an excellent addition to this.
Pretty neat, but the first thing I looked for was how to open a file in Python and it wasn't there. I'm guessing it's because the "File" column only displays methods on the file object, and open is a built-in function. I can see how this might be useful when context-switching between different programming languages.
Also the "Array" section refers to array.array objetcs, but, as there's no sepparate section for "Lists", they can be confused. Worst thing about this is that .byteswap would seem to be a list method (I know it isn't, but someone who's just beggining may be confused as to way the list doesn't have a bytewap() method!)
How does one define a cheetsheet when programmers aren't able to figure out how code works.
Would be nice to see Julia, Racket, or even a Scheme.
This is pretty sweet. It's like a super lite IDE but on paper.

For C#, in the online section, you should put a link to http://www.dotnetperls.com/. It also has sections for other languages.