When (and when not) to reach for Redux
I am a huge proponent of a couple of specific ideas. One is that you should always try to understand what problems a specific tool is trying to solve... And another is that you need to understand exactly what problems you are trying to solve in your own application right now, and pick the tools that solve your problem ...
logged by jerodsanto 2020-10-28T16:01:18Z #react +1 #javascript This is a fancified excerpt from Mark Erikson on JS Party #146 . Mark maintains Redux & Redux Toolkit and has been lovingly called, “Tech Support for the React Community”. To get the full experience you should listen while you read. 🎧 Click here to listen along while you read. It's better! 🎧 I am a huge proponent of a couple of specific ideas. One is that you should always try to understand what problems a specific tool is trying to solve, and part of that is… “What is the time and the context and the reason why this tool was ev
saved by
related reading
- Redux Essentials, Part 1: Redux Overview and Concepts | Reduxredux.js.org
- Redux Fundamentals, Part 1: Redux Overview | Reduxredux.js.org
- Application State Management with Reactkentcdodds.com
- You Might Not Need an Effect – Reactreact.dev
- Building data-centric apps with a reactive relational databaseriffle.systems
- Tao of React - Software Design, Architecture & Best Practices | Alex Kondovalexkondov.com
- Blogged Answers: A (Mostly) Complete Guide to React Rendering Behavior · Mark's Dev Blogblog.isquaredsoftware.com
- A guide to the React useReducer Hook - LogRocket Blogblog.logrocket.com
- Mediumtoyesebalogun95.medium.com
- A data race that doesn't compilecorentin-core.github.io
- The Conductor Rewrite: What They Changed to Make It Fastperformance.dev
- Join the dirtyverse: What is the creator economy?dirt.fyi