Contents
Code on this site shows up in two places: course lessons and regular blog posts. The article stays an article — theory, commands, walkthroughs. Next to fragments worth typing by hand you will see an explicit “Type in trainer” link. Other code blocks in learning material often carry a soft link to the trainer landing page — “Code typing trainer”.
Ritual
- Read why the fragment is in the post.
- Open the link — the reference loads in the trainer.
- Type to a full match; watch accuracy, not only WPM.
- Return to the text. If the material has a companion repo or local checks, assemble the file on your machine and run tests there — not in the browser.
Courses and the regular blog
In courses, practice blocks are often tied to lesson files: a short slice → typing → the full file in a repo. In ordinary posts the trainer link is a way to stop skimming and lock syntax, even when there is no lab nearby. Terminal output, bash, and unmarked fences stay copy-only — they are not drills.
What the trainer does not do
It does not install dependencies, clone a repository, or replace your terminal. There is no language sandbox in the browser on purpose: a real environment stays local. The site links prose to typing; packages and hardware stay with you.
Start here: the trainer landing page. For modes (full, memory, fillblanks…) and a weekly practice ritual, see the modes guide.
Comments