A desk that measured 162 context switches an hour

Our next request had nowhere to go. The central hub screen was locked while it worked through another problem, and we were hunting for a place to type.

We had treated that blockage as a missing interface. We thought a fresh hub would get us moving, but it would have created another place for work to hide. The trouble was more literal: we could not see the working desk as a working desk. Sessions, windows, queues, and the text box that started the next job all existed, but they made us reconstruct the moment from different screens. We could drill into a department after we knew where to look. We could not reliably see what was happening across the monitors while it was happening.

A map of four monitors

The original requirement was more mundane than observability. We wanted a live record of what software and tabs were on each monitor, plus their relative locations and sizes. That scope gave the desk a bounded contract. A map of four monitors did not need to infer intent before it could be useful. It could first reduce the scavenger hunt that starts when a session is visible somewhere but the route into it is not.

So we built the thing in front of us. The new desk drew four monitors to scale, then put a named tile for each session on the relevant space. Clicking a tile opened its details without making us hunt for that window.

The window records carried the distinction the map needed. rect described the operating system’s positioning space. visible_rect described the DWM frame on screen. Each record also carried onscreen, on_attention, and foreground status. A foreground window had keyboard focus and was marked as something the desk must never move.

The first measured hour

That was supposed to be a visibility tool. It quickly became an attention recorder. The first measured hour showed 162 context switches, an average of 23 seconds on a window, and Discord taking 43% of the switches. We had expected the desk to make our working state easier to navigate. It made the fragmentation visible as a count that was hard to explain away. The map could show a healthy looking grid while the attention log showed the grid being abandoned again before a thought had time to settle.

The tile position was never evidence

Then Codex challenged the model underneath the picture. We had treated geometry as identity: where a tile sat was used as evidence of which task and session it represented. Codex called that core design unsafe. The live sample produced confident but wrong task to session pairings, and the review found four things the feed was claiming without actually knowing them.

A scaled rectangle can show placement. It cannot prove provenance. We had been reading those pairings as fact for as long as the map existed, deciding which window to trust based on a tile position the tool was never in a position to verify. Once we did, the boundary was clear: the desk could report what the display gave it and leave the unsupported connection unclaimed.

Two failures a tidy would have missed

The review was not the only place the display exposed stale assumptions. The desk grid began sorting by session date and stopped skipping minimized windows. A display broker could place pages on the large monitor without taking focus or evicting what was pinned.

Under that behavior were two state failures that a window tidy would have missed: a daily cron marked live sessions abandoned, and automation sessions never closed themselves. Fixing the picture without fixing those two sources would have made the desk more legible while preserving false status.

A preclose check found the same issue in the health path. The alarm called a healthy watcher dead. A dashboard that could draw every monitor, name each tile, and chart every switch was still only as useful as the state it declined to invent. We stopped treating the visualization as a control plane. It was an instrument with a precise job: show the displayed work, record observed attention, and make any inference earn its evidence.

The scene we trust most

The final scene was smaller than the four monitor map, and it’s the one we trust most, because it doesn’t try to explain itself: a desk lease stale for 65 minutes, three lanes queued behind it, no inferred story about why. Just the number, and the queue it was blocking.

Ask of any status display what it observed and what it inferred. A lease stale for 65 minutes is a better thing to show than an invented explanation of it.

dxdev LESSON · paste into your AI coding agent
LESSON: A Visibility Tool Can Turn Into an Attention Recorder You Didn't Ask For
SOURCE: dxdev.com/blog/live-desk-attention-recording
WHAT HAPPENED: A desk map was built with a bounded contract (draw four monitors to scale, place a named tile per session, record onscreen/on_attention/foreground status) to fix a navigation problem, finding a window when it existed but the route into it didn't. Once running, it also measured 162 context switches in the first tracked hour, 23-second average attention per window. A separate review found the design had been treating window geometry as task identity, meaning the display could produce a confident but wrong task-to-session pairing, a rectangle proves placement, not provenance. The fix was narrowing the tool's claims to only what it could actually support: show displayed work, record observed attention, and leave any inferred task/session connection unclaimed rather than guessed.
THE RULE: A monitoring or visibility tool's on-screen position for an item (a window, a job, a request) is not the same fact as that item's identity or ownership; treating "where it's rendered" as "what it is" produces confident-looking output that can be wrong in ways nothing in the display will flag, so any inferred connection needs to be explicitly weaker than a directly-observed fact, not presented with the same confidence.
CHECK MY CODE, then report PASS or FAIL with file:line for each:
  1. Any dashboard or monitoring display that infers an entity's identity, task, or ownership from its screen position, sort order, or grouping, rather than from a directly verified source.
  2. Any status field (healthy/dead, active/stale) whose source is a heuristic (an age check, a cron-set flag) that has not been checked against ground truth recently, risking a healthy thing reported dead or an abandoned thing reported live.
  3. Any personal or operational metrics tool whose output revealed an uncomfortable real number (a fragmentation rate, an error rate, an abandonment rate) that hasn't yet been acted on.
THEN PRINT: a table (check, PASS/FAIL, evidence, fix) + a verdict (applies / partially / OUT_OF_SCOPE / no) + the single most important next action.