My (Joshua Tzucker's) cheatsheets and miscellaneous code snippets, scripts, etc.
Although I call most of these "cheatsheets", they tend to be more of the "things you might have missed" or "I wish someone had told me about x" type. Very few are actually written to cover the actual basics, but I often include a resources section at the top of each document with links to those kinds of guides.
Link for more info about how this site works.
I find that writing out a process or tip helps me remember it and cement the details of it in my mind. In addition, if I ever refer back to my notes, it is easier for me to parse my own style of note taking than others'. As such, everything in this repo was written with basically only myself in mind as the expected reader, so take it with a grain of salt.
I also tend to view swapping out more precise and accurate terminology with general descriptors, and even colloquial language or analogies, an acceptable trade-off for increased readability. I think in general, programmers get way too into terminology and end up alienating new coders by using unnecessary extra-precise terms for things that don't actually need them.
TL;DR - I tend to write in a simplified style for myself to read later, that might not always use the right terminology, but tends to get the basic point across. Not for everyone.
There are so many new things in tech (especially in web dev) to keep track of and learn. I've started a sheet of "elevator pitches" so you don't have to read through 10 paragraphs of marketing fluff just to learn what a new framework does.
These are some of my favorite places to learn new things, find other cheatsheets, or read about code in general.
- Favorite Sources
- Elevator Pitches