Attention is not inventory

In Vision, the argument is blunt: much of the industry survives by hijacking attention through dopaminergic reward pathways, then selling usage habits to whoever wants to steer market decisions. That is not a side effect. It is the product model.

Our greatest assets in life are our brains, so software that spends our attention for us and abuses our brains’ memory spans is very disrespectful.

That sentence is the HCI charter in one line.

Cognitive compatibility as a design requirement

End-user tools should be minimally invasive on attention. Developer workflows should keep cognitive overhead low. Programmers are users too. The most valuable resource in programming is the programmer’s time and creativity — not the computer’s processing cycles.

When software ignores those limits, we waste life “keeping up with the Kardashians” of toolchains, notifications, and engagement loops. The question that follows is not rhetorical:

Are we programming the computers, or are they programming us?

Complexity as a uniqueness failure

Vision also reduces complexity to a uniqueness problem: things that behave similarly should not be presented in vastly different ways. Rules exist so minds have a place to store memories. When every surface invents a new dialect for the same job, you are taxing working memory on purpose.

That is why HCI Nerdz cares about:

• Progressive disclosure instead of walls of options
• Consistent affordances across similar jobs
• Honest signals (severity, success, theme) so users do not spend cycles decoding lies

Heirloom software

The homepage creed on ryanjohnson.website still stands: software development is a craft. UX is of utmost importance in any technical system. Be kind to your future self. Every developer was once a user. Pass down maintainable heirloom software that a naïve reader can still understand.

Attention-respecting design and heirloom maintainability are the same obligation at two timescales: do not steal the present mind, and do not poison the future one.

Where this lives in the sibling stack

• HCI Nerdz — surfaces, themes, dialogs, IDE chrome, product representation
• OpenShellOrg — shells and CLIs that do not force stdout to be both pipe and canvas; progressive help budgets
• DevCentr — environments and toolchain management so practitioners are not drowning in accidental complexity

They stay separate on purpose — each one attacks a different layer of the same disrespect.