CSS for Software Engineers for CSS Developers
summary
Argues that stealing software‑engineering patterns makes CSS easier to maintain: use DRY via variables and mixins (preprocessors or PostCSS produce the single source of truth), split components by single responsibility (small composable classes instead of monolithic selectors), avoid DOM‑bound selectors and JS hooks for styling, prefer modifiers/responsive suffixes over nesting, enforce immutability (utility helpers with !important on utilities), and keep selectors short to lower cyclomatic complexity so changes scale without regressions.
AI-written summary · about
chapters (14)
- 0:00Intro
- 0:37Welcome
- 2:38FlowMatic
- 6:49DRY
- 14:47Single Responsibility Principle
- 20:43Separation of Concerns
- 27:55More HTML
- 30:14Immutability
- 36:23Cyclomatic Complexity
- 40:37Open Closed Principle
- 44:23Orthogonality
- 46:15Nesting
- 47:43CSS is not a programming language
- 49:04Questions
