Personal websites · BrowzerBooks editorial guide
Julia Evans’s blog: turn technical confusion into a small experiment
Use concrete explanations to investigate one behaviour at a time, then record what your own test showed.
Julia Evans
Julia Evans’s blog covers computing topics including Git, networking, command-line tools and learning. Her site also points to computer zines and exploratory projects. It is useful to readers who want to understand a confusing technical behaviour rather than merely memorise a command that appeared to work once.
Use a technical article to predict a result
For a post about a command or computing concept, write down what you expect a small example to do before trying it. Run only an example you understand in a safe test environment, then compare the result with your prediction. Record one surprise and the explanation you found. Avoid copying commands into a production system merely because they appear in an educational article. The useful reading outcome is a more accurate mental model, not a longer list of commands saved for later.
Try examples in a disposable environment
Follow current official documentation for commands that affect important systems, and do not run an unfamiliar example against production data. Blog posts explain a particular context and may become dated. Keep the distinction between learning experiments and operational work clear. The most useful outcome is an explanation you can reproduce, including what remains uncertain, rather than a copied command in a growing notes file.
Official source: Julia Evans.
Pause and try it
A command gives an unexpected result. What makes a better learning note than “it does not work”?
Reveal a possible approach
Record the input, expected output, actual output and relevant version. Reduce the example to the smallest case that still shows the difference, then investigate that case.
Public sources checked: