Most engineers I admire share one habit: they ship small things, often, in public. Not Twitter threads. Not announcements. Things you can use, or read, or run.
The cadence matters more than the size. A weekly rhythm is the smallest unit I’ve found that forces both intake and output. Anything slower and the work pools up; anything faster and the work goes shallow.
The two failure modes
Reading without building rots. You absorb concepts, nod along, file them away in the part of your brain that never gets tested. Six months later you can’t actually do the thing.
Building without writing forgets. You ship the code, move on, and lose the why. The next person — including future-you — has no map.
A weekly build forces a small read, a small build, and a small write. Three habits, one cadence.
What “weekly” actually means
It does not mean a polished essay every Friday. It means:
- One thing entered the world that wasn’t there last Sunday.
- The thing has a name.
- The thing has a date.
- The thing is on the record, even if the thing didn’t work.
Some weeks the build is a 200-line script. Some weeks it’s a diagram. Some weeks it’s a written-up failure. The constraint is the cadence, not the form.
Why public
Private practice drifts. Public practice has a reader, even if the reader is just future-you opening this page in 2027 and asking what was I working on?
The site is the trail.