← All writing · All tags · Atom feed

Attention, friction, and neurodivergence in the IDE

April 2026

accessibility cascade ide

This note connects three themes: Cascade IDE’s cockpit-inspired attention model, the idea of friction from the environment (not “bad people”), and neurodivergence —for example ADHD, which I mention because it is common in engineering samples and in public surveys.

It is not a claim that an interface treats a diagnosis. It is an argument that how attention is structured in software changes the cost of staying oriented—and that cost matters for many brains, including neurodivergent ones.

What “attention contour” is trying to buy

The cockpit metaphor in Cascade’s attention model is about roles, not wallpaper: a stable forward / editor anchor, secondary surfaces you open on purpose (MFD-shaped), and a consolidated alerting channel (EICAS-shaped)—instead of every tool fighting for the same z-order.

That targets a familiar pain in knowledge work: context switches, competing demands, banner blindness, and the slow rebuild of “what mattered last.” Those pains show up in qualitative work on software engineers with ADHD and in large self-report surveys (e.g. Stack Overflow Developer Survey items on concentration/memory—often cited in academic papers at roughly ~10% of respondents; compare to general-population ADHD prevalence estimates, which are lower and methodology-sensitive).

Nothing here replaces a clinician. The point is narrower: if a profession clusters people who struggle with sustained attention under interruption-heavy UIs, then an IDE that externalizes priority and state is not a niche luxury.

Friction-first, environment-first

The same line of thought appears in work on friction in products and processes: systems fail when the environment makes the wrong behaviour easier than the right one. Reducing spurious friction—predictable places for truth, fewer surprise surfaces—is aligned with that stance. Knowledge base, trust, and curiosity spells out provisional trust and inspectable ground between human and agent.

Where this may overlap with ADHD / neurodivergence (carefully)

Executive-function challenges often include restarting after interruption, prioritizing under noise, and holding several channels in mind. A UI that separates primary work from secondary tools and centralizes alerts does not “fix” ADHD—but it can lower the tax on the same skills that interruption taxes for everyone, sometimes asymmetrically.

Parity with the toolchain helps too: less re-derivation of reality from chat prose, more shared artefacts (tests, diagnostics)—another form of externalized state.

What this is not

  • Not a substitute for accommodations, coaching, or medical care.
  • Not a promise that one layout fits all: neurodivergence is heterogeneous; some people need flexibility and density controls, not only structure.
  • Not finished product evidence: Cascade is in development; this is a design rationale bridge for readers.