Taste Is Care, Not a Gift
Figma's chief design officer reframes taste as care, not gift, and names three things she screens for when hiring.
The small moves and tuning passes that separate good from generic.
20 entries
Figma's chief design officer reframes taste as care, not gift, and names three things she screens for when hiring.
Sheta Chatterjee walks through the design calls behind Gemini Enterprise: a shared AI inbox, team project spaces, and keeping people in control.
Elizabeth Goodspeed argues writing is another way to work through the same questions your design already circles, and well worth the effort.
After three decades built around the handoff, Jamieson Rothwell now ships working software and treats those build choices as design decisions.
Jeff Humble gathers a hiring playbook where every tip is from this year, aimed at senior designers rethinking their career strategy.
As AI flattens production, the author argues cultivated taste and a clear point of view become a designer's real edge.
A founder argues the real shift is encoding brand rules and taste into reusable files non-designers can run.
Notes from ÌníOlúwa Abíódún's talk on shipping AI agents: scope sharply, write to think, then explore rough prototypes.
Five lessons from serving 127 million customers, where hiding complexity is a deliberate architectural and cultural decision, not polish.
GitHub's five-year accessibility program turns outward, with audit data, design tooling, and AI agents making inclusion operational rather than aspirational.
A short, honest reflection on stalls, rebuilds, and why recalibration, not uninterrupted success, is what separates senior designers.
AI reads your design system differently; structured metadata beats prose documentation. · Foundations should be always-on; components served on demand through an MCP.
Most design systems are a shared palette and a Confluence page nobody trusts. · A real system enforces its contracts; agents expose every gap you papered over.
GitHub's accessibility agent reviewed 3,535 PRs at a 68% fix rate. The sharper lesson is what they taught it not to touch.
Agents read structure and naming, not docs or goodwill. The informal contract that held design systems together becomes a hard boundary.
Microsoft consolidated Copilot into four surfaces tied together by a 'Throw and Catch' pattern. The pattern, not the components, is the system.
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 spent years replacing plastic packaging with paper. The commitment was easy; getting every millimeter to behave was the actual work.
Rauno tried to solve 'scroll back' with a minimap. The minimap caused jank, the jank needed a blur, and the blur almost worked.
Linear took designers and engineers to Athens and shipped a working build by Friday. The trust that made the loop close, not the offsite, is what's worth lifting.