I’ve created a few quick-reference articles and it might not be clear why. There are a few reasons:
- These articles are mainly a reference for me. I find myself searching the same things over and over, looking for the purple link, scrolling through the article, then copy & pasting code. I’d rather not go through the hassle. These articles aim to solve that problem.
- I aim to keep the answers above the fold. I don’t want to have to scroll down to find the answer. I almost never read the surrounding prose when I am in “coding mode”.
- I don’t have ads or popups on my blog. I will never ask people to sign up for a newsletter or login to read more. I also don’t use pictures unless there’s a good reason. The “thinking AI robot stock photo” industry is definitely a bubble.
- Writing these things out explicitly helps me to remember them. Paradoxically, this may make these how-to pages less useful to me, but maybe someone else will find them useful.
These quick reference articles don’t explain much because I don’t need an explanation of what is going on. I just need a chunk of working code. There are other websites which have far more comprehensive guides covering how to do things. They cover all of the fundamentals of how things are done. But I don’t need that, I just want a 30 second reference with a working chunk of code.