I Pressed ⌘B. You Wouldn't Believe What Happened Next
summary
Pressing ⌘B becomes a long sequence of decisions: which numeric weight corresponds to “bold,” how to pick between local Google or org-shared fonts, what to do when only 400 and 800 exist, and whether to synthesize thickness when no bold exists. Expect concrete outcomes: command B jumps from 400 to 700 when available, font metadata lies about language and italics, examples of broken letters in multiplayer, and a real fix that required tracing installed font files.
AI-written summary · about
chapters (13)
- 0:00Introduction to typography
- 1:09The complexity of font weights
- 4:05Standardization in typography
- 5:15Algorithms for bolding
- 7:27Real bolding vs faking it
- 8:48Font sourcing challenges
- 10:03Multiplayer font conflicts
- 13:05Handling messy metadata
- 14:58Italics and edge cases
- 16:18The emotional toll of bugs
- 18:02Debugging the command-B issue
- 20:05Analogy to urban planning
- 22:57Embracing imperfection
related talks
51mI pressed ⌘B. You wouldn’t believe what happened next
43mCracking the Code
42mTypography for Frontends
40mCurious Findings
50mType-setting in CSS: Using typography to enhance your design
51mProblems solved by OpenType
01h 03mFonts, Form and Function: A Primer on Digital Typography
52mPutting the Fonts into Webfonts