Senior designers need technical literacy — understanding what's hard vs. impossible¶
Insight: Tisza argues that senior designers face obsolescence unless they understand technical constraints — though full coding ability is not necessary. The critical distinction: "You don't need to code. You need to understand what's hard versus what's impossible." Designers should understand rendering mechanics, state management, API limitations, websocket complexity, and performance implications of design decisions. Without this literacy, designers risk becoming "visual decorators" replaceable by AI.
Detail: Real-world failure examples: a designer specifying a three-month interaction without understanding architectural constraints; requests for real-time collaboration features ignoring websocket complexity; pixel-perfect animations that violate accessibility standards; infinite scroll implementations destroying performance. "The best designers I worked with don't write production code. But they understand rendering, state management, API limitations." This represents a technical product designer who bridges communication gaps between design vision and engineering reality.
Sources
Related: return-of-ux-unicorn in design-engineering.md — CORROBORATES