Better Production Decisions with HTML & CSS
summary
Claims that rewrote twitter.com in four weeks and that most design decisions get overridden in code (quotes a joking 94.3% figure) and shows why coding sooner matters: consolidating sidebar modules reduces CSS, prototypes expose real API data, and user tests on devices cut meetings. Builds native‑ready assets using border-image for native assets and -webkit-image-set, cuts branches off production so prototypes use real classes, and publishes a small toolkit (see ratchet UI toolkit) and experiments with Framer for interaction.
AI-written summary · about
chapters (16)
- 0:00Intro
- 0:25Who is Connor
- 8:35New New Twitter
- 16:14Why Code
- 17:24Real Data
- 17:39Systemic Design
- 18:21Designers vs Developers
- 19:06The Real Thing
- 19:34throwaway work
- 21:42mini button
- 22:32desktop app
- 24:12CSS
- 24:58Button Assets
- 25:39Border Image
- 26:39Vendor Prefixes
- 27:19Tools
related talks
21mStuff About Cascading Style Sheets
48mDo we have to reinvent the wheel?
24mScalable CSS: Challenges and Rewards of an Uphill Journey
51mModern CSS Development: Tooling & Workflows
29mPreprocessors, Components, and CSS in JS or: How I Learned to Stop Worrying and Love the Website
33mThe Purification of Web Development
29mModern CSS - A fireside chat
19mThe Shady Web: Using CSS for Good, not Evil