When 'feels instant' is the spec
Most performance work chases tail latency. GitHub Issues reframed it around distribution shape, then named 4.7% server/cache divergence as the price of feeling instant.
The shared building blocks design teams maintain across surfaces.
6 entries
Most performance work chases tail latency. GitHub Issues reframed it around distribution shape, then named 4.7% server/cache divergence as the price of feeling instant.
Microsoft consolidated Copilot into four surfaces tied together by a 'Throw and Catch' pattern. The pattern, not the components, is the system.
AI-generated code defers cost, it doesn't reduce it. Seven debt categories concentrate far from where the velocity gain was booked, including reviewer fatigue and security debt.
Most teams treat canvas, code, and PRD as three competing artifacts. Brett McMillin's reframe: a connected system, with an agent translating between them and the designer's judgment moving through both.
AI-readiness isn't a separate category. The same fundamentals (tokens, layout intent, accessibility, governance, handoff contracts) finally have to read clearly to a non-human.
Microsoft spent years replacing plastic packaging with paper. The commitment was easy; getting every millimeter to behave was the actual work.