Welcome to my (Joshua Tzucker's) collection of personal cheat sheets, technical documentation, and miscellaneous code snippets. Unless indicated otherwise, all content is written and collated by myself.
You can use the directory menu (top left button) to easily switch between pages on the site.
Although I call most of these pages "cheatsheets", they actually come in a wide variety of "flavors". The vast majority of them are indeed cheat sheets / quick reference pages / technical docs, but the full list includes:
- Cheat Sheets / Technical Documentation
- These make up the majority of the pages
- Example: TypeScript Cheat Sheet
- In depth guides / lessons
- Example: Intro to JWT
- Lists and collections
- Example: "Favorite Programs"
- Code Snippets / Gists
Elevator Pitches - Link
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.
Favorite sources - Link
These are some of my favorite places to learn new things, find other cheatsheets, or read about code in general.
At the footer of each page, including this one, is a link to a feedback form. It should auto-populate with the URL from this site. Please let me know if you spot any errors or have any feedback to provide!
Note: Currently, the below list is not automatically generated. However, the directory list that you can access through the menu toggle (top left button) is automatically generated, and should be exhaustive, based on my source filesystem.
- Favorite Sources
- Elevator Pitches
- QT / QML
- Misc (Includes things I often forget)
- Node and NPM
- Network requests
- Newer Stuff
- Promises and Async/Await
- Google Apps Scripts (GAS)
- JSON Schema
- UI Development & Design
- Authentication / Security
- Cloud Services
- Non-Tech / Completely Random
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.