You have a couple of cheat sheets of mine in your directory, which I appreciate. However, you directly link to the PDFs. It would be nice if you included a link to my site that lists the sheets I've made. Maybe on the source page for my name?
No problem. There is currently a link to your blog from the source page. Would you like me to change this link to your cheat sheet list? Or are you talking about a separate link?
In general, I try to avoid direct links to PDFs except when it is unavoidable or confusing for the user. If there were separate landing pages for each cheat sheet, I could remove the direct PDF link and link to those instead.
I like it. Clean layout, easy to find what I was looking for (even searched for Clojure).
But is this merely an aggregation of cheat-sheets off of the web? Is there any review process involved before a cheat-sheet shows up on your list? I guess what I am getting at is how is this different from me just searching google for "emacs cheatsheets"?
Yes, this is a cheatsheet aggregator/directory from cheatsheets around the web. Each cheatsheet is manually reviewed to make sure that it is useful and relevant. I think it is important to maintain a high quality level in the directory or else it defeats the purpose. In the future, I hope to add sorting by popularity to make it even easier to find the top results.
So why is this different than a google search? Well, in my experience, Google does not return the best results for cheatsheets. This may be partially due to the fact that many are downloads in PDF or other formats, so the relevant content may not help with SEO ranking. Another advantage is that devcheatsheet.com provides a preview before you click through and download. Finally, it is also easier to navigate between related topics such as Javascript and JQuery.
Great! Thanks for the response. I really like the site, and I agree with you that Google does not always lead to a good answer each time.
I wonder if a "Was this useful for you?" feature might be a good idea. I say this in response to your "sorting by popularity" comment. I guess you could use a voting system too.
No, right now I am the only one who approves new content, even in languages that I am not familiar with. Reviewing every command in every cheatsheet would be a very difficult and time-consuming process.
In general, I have not noticed many inaccuracies in the cheatsheets other than typos or small errors. If there are errors, then hopefully users will contact the author and he will update it or issue a new version.
As I've mentioned in other comments, I also hope to add either community voting or popularity indicators to help identifiy the best (and presumably most accurate) cheatsheets for each language/tag.
Version 2.4 is near the top. Even if that was the most popular cheat sheet, there should be some way to have references for newer versions at the top. I know it's a tough problem that Google hasn't cracked even, but it would be nice to have addressed even with a workaround like a version keyword for each cheat sheet and then a list of versions on the right side.
I agree that there needs to be a way to easily distinguish between versions. I am planning to add version keywords but haven't gotten to it yet. Also, I hope to add more sorting options too, such as date created, which might also help.
I agree. My next big task is figuring out the best way to rank the most relevant results for each tag. I am looking into several options including voting and an aggregation of other popularity factors (# clicks, # bookmarks on delicious, # links, etc).
If you are looking to evolve the site here are some suggestions: Create an online editor in javascript or flash that lets your users create and edit cheat sheets online. Leverage a CC license so your users can print and spread the created cheat sheets (free advertising). Sell prints (photos), mousepads, booklets etc. While offering free products or a monetary reward to the authors (threadless style). Also let the author give their reward to a related organization (like the python software foundation for a python cheat sheet). Keep user participation high and the site organized with tagging and ranking features.
Most of your visitors will be coming because they want to learn a language from a cheat sheet or have a quick reference. This seems like a great target audience for Amazon links. If you had 2-3 books you recommended in the right sidebar for each category, I think that might fare better than Google Ads. Could be worth A/B testing.
The Google Ads are just a placeholder. I think Amazon books would be very relevant, and I am going to look into some other affiliate programs such as thinkgeek.com.
I like it. Though I feel that some of these guides don't really qualify as cheat sheets. I consider a cheat sheet to be a quick reference with helpful commands, syntax, examples etc. Some of these documents are just condensed howto guides. For instance, most of the SEO ones. Something to think about anyway.
Nice site. Have you considered incorporating any interaction with the site, such as a way to rate the cheat sheets or give comments? Also, it (might) be cool if there was the ability to create user/community driven cheat sheets that could be modified wiki-style or something.
Like it. There's a lot of content and it's well organized.
It would be nice if there was more information on each cheat sheet before I clicked it. Maybe a list of things that are in it (Class Functions, String Functions, Regex Expressions for example). Or add more tags to each cheatsheet.
Thanks for the input, Vindexus. I have considered adding a short description to each cheatsheet, and I intend on adding additional tags as well. However, I am trying to be cautious and maintain the clean look without overwhelming the user with information. It is always a balancing act.
Of course, that makes sense. How about a "Preview" link that uses Lightbox or Fancybox to bring up a cropped screenshot of the cheatsheet? Just so I can get a look at some possible things they'll cover and the format of it. Not a huge deal, and probably a bit of work just to get the sceenshots.
Good job on making a nice and clean design! One thing I found slightly confusing was that some images of cheatsheets links to an intermediate page, instead of the cheatsheet itself.
I'm gussing it is because these have different formats. One suggestion would be to pick one of them (e.g. PDF) for the image, and create links on the different formats (e.g. "Formats: DVI, PDF, TeX") for alternative formats.
Very useful, but the :: separators are distracting. I think that most first-time visitors are looking to scan your collection for a particular technology (that's what I did).
This view [http://devcheatsheet.com/?view=tag] is more readable. How about using the 'tag' view layout, but add categories to make browsing easier.
Another suggestion: add 3 or 4 'similar cheat sheets' to each cheat sheet to facilitate browsing and reduce bounce rates.
It looks like this is a well-named niche bookmark browsing site. I looked for more detailed About, but could only find the rather terse text mentioned at the bottom of each page. Do you personally do the maintenance and curation?
I don't mind at all if you (Tim Church) do it, its just important to know whos opinion forms the content and how well any broken links or tech advances will be catered for.
Good work BTW, no matter who has the keys to Djangos Admin Interface!
What I'd like is being able to type in a big search textbox sth like:
"java try catch syntax"
and it would automatically (without me hitting enter) fetch the sample code and display it in a nice syntax-highlighted manner. It should also offer auto-completion like Google (eg. after I typed "java try"...).
Or:
"php class syntax"
"svn ignore files"
"diff show side by side"
"c++ template function"
etc.
It'd be a lot of work but it seems doable and it'd be a killer destination site for programmers.
Thanks for the input. The examples you mentioned are more similar to the tags view (http://devcheatsheet.com/?view=tag), which is not currently the default.
Within minutes of discovering this on HN I needed a cheatsheet for RoboCopy. Didn't find one on your site. For what it's worth here's a pretty good one I dug up http://ss64.com/nt/robocopy.html
This is really convenient, very well done. Is there any way we could network a text editor such as TextMate, to pull context help depending on the file/language you're currently using? So you press F1 and it would send you to the appropriate PDF...?
This is an excellent resource and done very professionally. I like the clean site look and nothing is more than two clicks away. Surely it will be a winner with developers.
Let us know when your new year's resolution traffic is on target! Nice blog too:)
I'd like to see the date the actual cheatsheet was created...not just added to the site. A javascript cheatsheet from 2001 is likely to be much different than one from 2007. Other than that I love the site!
Adding the date created is on my todo list. This information might not be available for every one, but it would be useful for the ones that do have it.
Some of the Javascript material is very old, and refers to Netscape as a going concern. Sometimes old is interesting but perhaps there could be some markers to warn people.
Any chance for a QT entry in the Libraries & Frameworks section? That's defiantly a framework worth noting, but I'm not sure how much cheatsheets are out there for it. They are kind of hard to find.
Seems that you are currently hotlinking the cheatsheets from other sites. imho it would be nicer to host the files yourself, to prevent link rot and to not "steal" other peoples bandwidth.
Whenever possible I try to link to a download page instead of directly to a PDF or image file. However, in some cases I do hotlink directly to a file download. One advantage of this is that if the author updates the file (to fix an error) the user downloads the newest version.
What do other HN'ers think? Should I host the PDF files directly? What is the proper netiquette in this case?
Maybe you could do it Google-style, where you feature the hotlink but also offer a cached version of it. Or, alternatively, you can hotlink to Google's cache of it (since they almost certainly have one!).
Thank you HN! I really appreciate all of the positive feedback and creative suggestions. Your comments have given me lots of ideas and the encouragement to keep improving the site.
excellent work, just bookmarked it. The only thing I'll recommend you is to improve that adsense there or look for a new revenue model, you won't earn much from it at the place it is, maybe sell ebooks later: kind of the "devcheatsheet book".
I've debated adding community features like voting or comments on the cheatsheets, but I haven't decided yet. I may experiment with some of these features in the future.
There is currently the option for anyone to suggest a cheatsheet that is not currently in the directory. (So if anyone sees a missing cheatsheet, let me know!)
