Earlier quoted context omitted.
Yes, writing it down.
you learn it by writing it down.
The act of writing down your own cheat sheet helps you to learn it.
Unified access to the best community-driven cheat sheets repositories
71–80 of 87 posts
Re: Unified access to the best community-driven cheat sheets repositories
#72I like the idea, and think it has potential, but… The search engine is not great. The tutorial gives the example of searching for "execute+external+program". Change "program" for "command", you're OK. Change "execute" for "run"and it bombs. For something that simple, this causes doubt that if I were to look for a solution to a problem in a language I was learning and it bombed, is the fault with cht.sh, or with me? D…
I agree about the search engine. I'm a big fan of Dash, but Dash is currently built around documentation rather than cheat sheets. If someone loaded up Dash with a bunch of cheat sheets, that would be really handy.
Dash absolutely has cheat sheets.
Re: Unified access to the best community-driven cheat sheets repositories
#73Instead of investing in out of band resources like this, I really wish people would just contribute improvements to the upstream documentation, which is usually more comprehensive and up-to-date than any of these resources can be.
No, I don't agree. Git has great documentation but if you want to know how to use it you either spend 15 minutes reading the relevant part of the big free book or you Google for a cheat sheet. Same goes for vim. I don't know why but some people are satisfied with documentation which, although not incorrect, only makes sense when you already have a substantial understanding of the topic at hand.
Re: Unified access to the best community-driven cheat sheets repositories
#74Instead of investing in out of band resources like this, I really wish people would just contribute improvements to the upstream documentation, which is usually more comprehensive and up-to-date than any of these resources can be.
No, I don't agree. Git has great documentation but if you want to know how to use it you either spend 15 minutes reading the relevant part of the big free book or you Google for a cheat sheet. Same goes for vim. I don't know why but some people are satisfied with documentation which, although not incorrect, only makes sense when you already have a substantial understanding of the topic at hand.
Nonsense, you can also read the man pages, and if any of these resources are insufficient you should spend any time you would have spent writing a cheat sheet contributing improvements to the actual resources - the documentation is an open-source community project as much as the project itself is.
Re: Unified access to the best community-driven cheat sheets repositories
#75Earlier quoted context omitted.
No, I don't agree. Git has great documentation but if you want to know how to use it you either spend 15 minutes reading the relevant part of the big free book or you Google for a cheat sheet. Same goes for vim. I don't know why but some people are satisfied with documentation which, although not incorrect, only makes sense when you already have a substantial understanding of the topic at hand.
Nonsense, you can also read the man pages, and if any of these resources are insufficient you should spend any time you would have spent writing a cheat sheet contributing improvements to the actual resources - the documentation is an open-source community project as much as the project itself is.
Sounds like a bit of a waste of time to me. What are the odds Linus is going to update the git documentation with my list of handy shortcuts? He'll just swear at me. I don't think the official documentation is the place for it; not now it's been written the way it has. I'm happy with the book + my notes on gitlab.
Re: Unified access to the best community-driven cheat sheets repositories
#76Earlier quoted context omitted.
I agree about the search engine. I'm a big fan of Dash, but Dash is currently built around documentation rather than cheat sheets. If someone loaded up Dash with a bunch of cheat sheets, that would be really handy.
Dash absolutely has cheat sheets.
Holy cow! There's a whole category for them. How did I miss that?
Re: Unified access to the best community-driven cheat sheets repositories
#77Earlier quoted context omitted.
Nonsense, you can also read the man pages, and if any of these resources are insufficient you should spend any time you would have spent writing a cheat sheet contributing improvements to the actual resources - the documentation is an open-source community project as much as the project itself is.
Sounds like a bit of a waste of time to me. What are the odds Linus is going to update the git documentation with my list of handy shortcuts? He'll just swear at me. I don't think the official documentation is the place for it; not now it's been written the way it has. I'm happy with the book + my notes on gitlab.
Well, for one, Linus isn't the current maintainer of Git. It's currently Junio C Hamano , someone whose main responsibility in open source is looking after git, who has the time and inclination to review your contributions thoughtfully. Have you ever actually read a git man page? Or do you just get all of your git knowledge from scattered blog posts and cheat sheets? No wonder people think git is hard. Read a random git man page right now and you'll find it quite pleasant to read and containing a plethora of useful information.
Re: Unified access to the best community-driven cheat sheets repositories
#78Earlier quoted context omitted.
you learn it by writing it down.
The act of writing down your own cheat sheet helps you to learn it.
It seems like the chain of four comments starting with Quequau's (https://news.ycombinator.com/item?id=17505892) and ending with superflyguy's (https://news.ycombinator.com/item?id=17507512) mean to disagree, but actually wind up agreeing. Is that correct, or is there some subtle distinction among them that I'm missing?
Re: Unified access to the best community-driven cheat sheets repositories
#79I like the idea, and think it has potential, but… The search engine is not great. The tutorial gives the example of searching for "execute+external+program". Change "program" for "command", you're OK. Change "execute" for "run"and it bombs. For something that simple, this causes doubt that if I were to look for a solution to a problem in a language I was learning and it bombed, is the fault with cht.sh, or with me? D…
Using a commonly available bin like curl is great, but if codebase made me install something that would first run my query locally before hitting the net, that would be preferable. Because if I search for something, say ruby-related, then it's a good chance I'd search for something else later on that's ruby-related and having the command cache info locally would give me the same interface and quicker results later on.
Re: Unified access to the best community-driven cheat sheets repositories
#80Similar project: Bro pages, like man pages but short examples of common use cases instead of extensive documentation. http://bropages.org/
Thanks for the tip on that, bro! That will really come in handy.