How teams give feedback and choose between options under pressure.
11 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.
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 companies don't write down how they hire because writing it down forces honesty about what they actually value. Linear did the work and published it.
Frontier AI teams optimize what's measurable, not what matters. Microsoft's user researchers want a seat at the evaluation table, as a safeguard against the metric chosen for being convenient.
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.
Coding agents collapsed the implementation window. The alignment checkpoints that used to live inside it just disappeared, and the PR cannot carry their weight.
An engineer at Linear scopes coding-agent tasks tight enough that they can't wander. The discipline is the same as scoping for a junior teammate.
Maggie Appleton reads Steve Yegge's chaotic agent orchestrator as speculative design fiction. The coding bottleneck is gone; the design bottleneck was always there.
Nubank ran a real A/B test on whether to scale or shut down an internal HR product. The data was unambiguous; the team's reaction to it was not.
An engineer at Linear scopes coding-agent tasks tight enough that they can't wander. The discipline is the same as scoping for a junior teammate.
Rauno tried to solve 'scroll back' with a minimap. The minimap caused jank, the jank needed a blur, and the blur almost worked.
