2019-01-19
1570
#react#redux
Christian Nwamba
1815
Jan 19, 2019 ⋅ 5 min read

When (and when not) to use Redux

Christian Nwamba JS preacher. Developer 🥑. Building the web with the community @concatenateConf @forLoopAfrica. JS and Senior Advocacy for the Next Billion Users through Microsoft.

Recent posts:

how to protect your ai agent from prompt injection attacks

How to protect your AI agent from prompt injection attacks

Explore six principled design patterns (with real-world examples) to help you protect your LLM agents from prompt injection attacks.

Rosario De Chiara
Aug 27, 2025 ⋅ 5 min read
Don’t Let AI Erase The Next Generation Of Dev Leaders

Don’t let AI erase the next generation of dev leaders

As AI tools take over more routine coding work, some companies are cutting early-career dev roles — a short-sighted move that could quietly erode the next generation of tech leaders if we aren’t careful.

Jack Herrington
Aug 26, 2025 ⋅ 6 min read

Qwen3-Coder: Is this Agentic CLI smarter than senior devs?

Discover Qwen3-Coder, Alibaba’s 480B parameter agentic coding CLI, with real-world tests, use cases, and performance insights.

Chizaram Ken
Aug 26, 2025 ⋅ 4 min read

daisyUI 5 is here: What’s new and what to expect

Explore daisyUI 5’s new features, performance upgrades, and theming engine built for Tailwind CSS 4 developers.

Ikeh Akinyemi
Aug 25, 2025 ⋅ 8 min read
View all posts

7 Replies to "When (and when not) to use Redux"

  1. Why would anyone EVER use redux? Because they aren’t aware of MUCH simpler ways to solve the same problems.

  2. What exactly did you show in the example please?

    – how redux dispatch is called -> OK, shown
    – how programming a reducer is used to modify a shared state (redux store) -> OK, shown

    But the most important thing is — where is the actual logic?
    Where is the functional programming you are talking about?

    I don’t see any functionality, just a way to store information into a shared state.

Leave a Reply