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

You'd go to DDG and type in "git cheatsheet".

Or for the ultimate in self-referencing cheat sheets, use:

https://duckduckgo.com/?q=ddg+cheat+sheet&ia=cheatsheet

This links to:

https://duck.co/ia/view/duckduckgo_cheat_sheet

I think this leveraging off DDG's goodies, part of their Instant Answers:

https://duck.co/ia?repo=goodies

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.

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.

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

When one is exploring domain specific command sets.