Shelf essay · correspondence
Devlog drafts & feedback ethics
A devlog is not a marketing ladder — it is a letter left on a shelf for the next person who opens the cupboard. These notes are about how we file half-finished ideas without pretending they are inventory.
Design drafts as correspondence
We keep three kinds of margins on early pages: one for mechanics, one for mood, and one for doubt. When a system is only partially true, we mark the boundary with language — “speculative,” “untested,” “borrowed from a jam build” — so readers do not mistake sketches for promises.
Versioning is emotional work too. A changelog can narrate panic and relief with the same monospace as bug fixes; we try to separate tone from telemetry. If a feature dies, we write its obituary in one paragraph: what it taught, not what it cost in pride.
- Date the feeling, not only the commit.
- Caption screenshots with context, not slogans.
- Leave one blank line between fact and interpretation.
Ethics of feedback on unfinished work
Feedback should widen the author’s field of view, not narrow it with borrowed authority. We ask for observations before prescriptions, and we name our vantage point — platform, culture, fatigue level — the way a cartographer notes projection distortion.
Public threads reward wit; they rarely reward care. When critique touches identity, labor conditions, or access to tools, we move to slower channels. The shelf is public, but some annotations belong in the margins of a private letter.
We refuse the performance of omniscience. The best note on a draft often sounds like: “Here is what I felt at minute three, and here is what might be unrelated to your intent.” That pairing — sensation plus humility — keeps feedback from becoming a costume.