Blog

Essays and observations — not release notes. For org updates, see News.

  1. Sequence as the top-level: pipeline composer interfaces

    When a system applies rules in order, the processing-map surface should show that order as one spine — not scatter steps across settings pages until the machine contradicts itself.

  2. Share the IR, not the pixels: a strategy for multi-ecosystem UI prototypes

    For interaction-heavy prototypes, share meaning and behavior — domain IR plus a headless controller — and hand-write thin views per ecosystem. Do not aim to auto-convert full UI.

  3. Fundamental contexts for portable UI

    Maybe portability is not one mega-spec but a small set of fundamental contexts — structure, placement, events, 2D/3D surfaces, zoom — composed on purpose.

  4. Attention is not inventory

    Software that spends your attention for you is disrespectful. HCI should treat cognitive budget as a hard constraint — not a growth funnel.

  5. Human intuition over backwards convention

    Consistency with the past has value — but it is not absolute. When a convention inverts human meaning, fix it.

  6. The bug is product representation

    When capability exists but the first-class UI hides it, the product is lying about what counts — and that is an HCI bug, not a power-user gap.

  7. When 'non-technical' products lie

    Marketing a tool as friendly while forcing archaeology through CSS hierarchies and secret modes is an HCI failure — not a documentation gap.

  8. Theme is a contract

    Previews, diagrams, and chrome that refuse the host theme are not aesthetic preferences — they break immersion and trust.