Crafting Pristine React: Best Practices for Maintainable Code
summary
Shows concrete fixes: encapsulate Redux with use-data custom hooks and avoid leaking React Redux everywhere, replace manual memoizing with measured profiling and try Million or wait for React Forget only when needed, add at least one E2E using Playwright for critical flows and run axe-like checks in dev, move business logic out of components into framework-agnostic services or clean-architecture modules, and enforce kebab-case filenames and import aliases to prevent CI-breaking case bugs.
AI-written summary · about
chapters (26)
- 0:00Intro
- 0:49Working with React
- 2:48About React
- 3:43Disclaimer
- 4:48Estates Management
- 5:35Final Replace
- 6:12Hooks
- 7:23Do not leak
- 7:46Component performance
- 8:47React compiler
- 9:04React Memory
- 9:16Virtual Dome
- 9:55Premature Optimization
- 10:24Testing Accessibility
- 10:48Testing Tools
- 11:35Accessibility
- 13:06Logic Business
- 13:55Custom Hooks
- 14:38Agnostic Logic
- 15:15Clean Architecture
- 17:17File Structure
- 18:12Case Sensitivity
- 18:30KCase
- 19:30Import Alysis
- 19:55Folder Structure
- 21:31Advent Calendar
related talks
12mReducing bugs in a React codebase
53mHelp! My React app is slowwwww!
44mA Practical Guide for Crafting Resilient UI Components
15mReact Best Practices in 15 Slides
32mRefactoring React
51mReact & Redux: Optimizing performance
34mSecrets of building robust UI components
42mClean Code vs. Dirty Code: React Best Practices