Default to Consistent
summary
Argues that strong, opinionated conventions reduce decision fatigue and keep velocity as teams scale, supported by concrete tools and patterns: enforce styles with ESLint rules, scaffold features with generators like Ignite or code mods via TS Morph, and prefer documented duplicate implementations before refactoring. Shows a real refactor—moving navbar bits into leaf components to avoid screen re-renders—and describes a Shopify pattern of send and store (actions in send, state in store) plus example hooks and generators that made large-scale changes feasible.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 1:41Design patterns and decision fatigue
- 3:48DRY and repeated decisions
- 5:52AHA and wrong abstractions
- 7:39Duplicate code and standards
- 9:24Code generators and examples
- 10:27Fundamental theorem of software engineering
- 12:55Shopify’s code conventions
- 14:18Code organization opinions
- 15:42React’s abstraction layers
- 17:29Tech debt and consistency
- 18:51Collaboration and humility
- 19:54Shopify’s state management example
- 21:17Explicit APIs and predictable behavior
- 22:40Grouping side effects with use actions
- 24:05Send and store pattern for mocking
related talks
43mScalable Best Practices for Your Development Team
25mPrinciples for Scaling Frontend Application Development
01h 01mDesign Principles for Better FrontEnd Code
40mBuilding resilient frontend architecture
26mGood Code
27mDesigning Even Larger (JavaScript) Applications
33mGet the core right and the resilient code will follow
28mVerbosity, Maybe the Key to Better Code