Get the core right and the resilient code will follow
summary
Argues that better, smaller CSS comes from nailing planning, async communication and feedback with designers rather than chasing new syntax; shows concrete practices: Slack/email wording that reduces interruptions, linking standards like WCAG AA, recommending tools like Figma dev mode and Stark for accessibility, and replacing fragile client-side tricks with a pragmatic hourly rebuild with randomisation of CMS content to avoid sliders and brittle JS. Gives a cautionary example of a rushed design system with three competing grid systems and fragile components.
AI-written summary · about
chapters (8)
- 0:00FF Conf welcome
- 1:05Soft skills over CSS features
- 3:31Design handoff culture outdated
- 7:31Communication is critical
- 17:22Feedback for design and code
- 26:18Slow down for maintainable systems
- 30:55Core skills for resilient code
- 32:42Closing thoughts
