헌집줄게, 새집다오
summary
Explains why a monolithic frontend with domain layered services becomes slow to build and hard to change and how splitting by service plus centralizing UI state into Redux reduces coupling while introducing new tradeoffs. Migrates from interface wrappers to concrete injections, adopts React Redux 7.1 features like useSelector/useDispatch, creates action utilities that autogenerate API action triads and slimmer reducers, and ships a scaffolding generator for new repos. Reports faster development feedback loops but ongoing refinements and occasional rebuild pain.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 2:17Current architecture benefits
- 6:16Need for structural change
- 9:33Repository split decision
- 13:12Why new structure
- 18:05Redux adoption limits
- 21:22Final structure rules
- 24:44Improving Redux usage
- 27:01Continuous improvement
- 28:31Summary
related talks
28mHow to teach an old dev new tech: Learning React as a senior developer
58mFrom Zero to Live with Functional JavaScript Applications (Part 2)
04mInterview with Swizec Teller
30mThe Awesome Struggles as a Front-end Engineer
14mFrom Angular to React, how i decided to take the next career step
11mInterview with Cory House
40mHow to sell a big refactor or rewrite to the business?
32mRebecca Murphey - SeattleJS Conference 2017