s4.codes — about
Asfar Ali
Senior software engineer. Educator. I make hard things easy to follow.
the practice
Small pieces, in the right order.
I build production software for a living — the kind that has to keep working long after the demo. What I do publicly is take the parts of that work that are genuinely difficult and break them down until they are obvious. Not simplified. Broken down.
Most explanations lose you.
And it is almost never because the subject was too hard.
The usual technical explanation is written by somebody who already understands the thing. They skip the step that stopped being interesting to them years ago — and that step is the one you were standing on. Nothing after it lands. You read the paragraph a third time, decide the subject is above you, and close the tab. The subject was never the problem. The explanation had a hole in it.
The curse of knowledge — once you understand something you can no longer remember not understanding it. Every explanation written from that side quietly leaves out the part that was actually hard.
Volume mistaken for depth — more slides, longer videos, thicker docs. The material gets bigger without getting clearer, and the ordering work is left to the reader.
Nobody enjoys it — technical material is allowed to be tedious by convention. But attention is the entire budget: if it is dull it does not get finished, and unfinished is the same as untaught.
Small pieces, in order.
How something technical becomes something pleasant.
The fix is not to make the subject smaller. It is to cut it into pieces small enough that each one costs almost nothing to accept, then put them in an order where every piece is already standing on the one before it. Done properly there is no moment where you have to take something on faith — which is exactly why it stops feeling like work.
One idea at a time — a chunk you can hold in your head whole. If a step needs two things explained at once, it is not one step yet.
Nothing skipped — especially the awkward middle, where most explanations thin out to a link and a shrug. That part is the job.
Show it, then name it — the thing first, the terminology after. A name handed over before the thing it names is just vocabulary to memorise.
Worth watching — pacing and restraint are not decoration on technical material. They are what gets somebody to the end of it.
Where it shows up.
Short form daily, long form here — same method either way.
Most of it lands on the feeds first: short, self-contained explanations of a single idea, made to be watched rather than endured. The longer work — the pieces that need room to build — lives here.
A subject you want covered, or a thing you have read three times and still cannot see — that is the useful mail to send.