Practical coding · build in public

Ship small tools. Learn by building.

Short tutorials, working repos, and checklists for people who want something running on screen — not another lecture hall.

Photo: oomlout / Wikimedia Commons, CC BY-SA 2.0

Learning paths

Each path is a handful of focused lessons. Finish one, deploy something real, then pick the next.

HTML structure, CSS layout that holds on a phone, and the few browser tools you will actually use.

Small Python and shell jobs that rename files, hit an API, or save you an afternoon of clicking.

From blank theme to sticky header, dual-crop hero, and card grid — with a live URL you can share.

Push a static page to hosting, prove the URL on mobile, and write down the three commands you used.

Turn a red stack trace into the one line that matters — then fix it without rewriting the whole file.

Editors, browsers, and checklists — only what you need this week. No tooling rabbit holes.

Every lesson ends with a runnable artifact — a page, a script, or a checklist you can reuse. We prefer short steps over long videos.

Pick a single outcome (deploy a page, parse a CSV, fix a layout break). Stop when that outcome is live — not when the playlist ends.

Localhost is practice. Share a public (or origin Host) URL and open it on your phone. If it fails there, the lesson is not done.

Write the three to five commands you actually ran. Next week you will thank yourself when the same deploy is muscle memory.

A plain text editor, a modern browser with DevTools, git, and a terminal. Optional: a static host or a WordPress child theme when you need a CMS.

Ship one static page with readable type (≥16px body) and a working mobile layout.
Automate one boring file job in Python or shell and schedule it once.
Read three error messages end-to-end and fix them without rewriting the project.
Document your deploy steps so a teammate can repeat them without asking you.