Full Stack Anxiety

The talk that named the feeling. A designer-who-codes traces the path from Neopets and Geocities to an industry that expects everyone to know everything, and offers a framework for deciding what to learn without the dread.

• The squeeze. T-shaped designers ("a specialist who can also do everything else") gave way to W-shaped ones—experts in two fields, plus the foundation in all the rest. The expectations are real and unsustainable.
• The real cost. Skills are a spider graph: every hour spent growing one axis shrinks the others through neglect. Choosing what to learn is choosing who you'll be employable as next year—which is why "what do I learn?" becomes full stack anxiety.
• Six ways through it: do the research (know the landscape before picking a direction); look at the big picture (five-year questions beat this-week questions); write it all down (open loops eat cognitive space—a stressful list beats a vague panic); take the decision out of the moment (if-then rules for learning, then obey the mighty list); stop chasing trends (tools die—invest in transferable, tool-agnostic skills); and be happy.
• The last one is the point. Should is what others expect; must is what keeps you up until 5 a.m. Sometimes a job can just be a job—the game side-project that taught him nothing useful for product design was also the thing that fixed the burnout. "Anxiety is the dizziness of freedom" (Kierkegaard, obligatory).
• Closing move: your career deserves the same care as any project you'd design. Don't wing it.