The parts of programming nobody assigns as homework.
Eight working notes on reading documentation, debugging, version control, small command-line tools, APIs and rate limits, keeping keys safe, writing a help page, and weighing the sources you learn from.
- reading
Reading Documentation Without Drowning
Documentation is not a book to finish. It is several kinds of writing bundled together, and knowing which kind you are holding saves most of the effort.
- debugging
Debugging Habits That Outlast the Bug
Any single bug is forgettable. The habits you use to find it are not. A handful of steady routines make the difference between an hour of guessing and ten minutes of looking.
- version control
Version Control Basics for One Person
Version control is usually taught as a team tool. It is just as valuable alone: it is an undo button that spans months and a diary you did not have to remember to write.
- tools
Writing a Small Command-Line Tool
A tiny program that does one job from the terminal is one of the best early projects. It is finished quickly, it is useful to you, and it teaches conventions that every larger tool relies on.
- apis
APIs and Rate Limits in Plain Terms
An API is an agreement about how two programs talk. A rate limit is the part of that agreement that says how often. Understanding both prevents the most common beginner mishaps.
- safety
Keeping Accounts and Keys Safe While You Learn
Learning to program means collecting accounts, tokens, and keys at a surprising pace. A few habits started early prevent the mistakes that are painful to clean up later.
- writing
Designing a Clear Help Page
Sooner or later every project needs a page that explains how to use it. The order of that page matters more than its wording, and good models can be found well outside software.
- reading
Judging a Source by Its Distance From the Subject
Learners depend on tutorials, forum threads, and reviews written by strangers. A simple question, how close is this source to the thing it describes, sorts most of them.