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:

SOLID Series: Liskov Substitution Principle (LSP)

A deep dive into the Liskov Substitution Principle with examples, violations, and practical tips for writing scalable, bug-free object-oriented code.

Oyinkansola Awosan
Jun 6, 2025 ⋅ 10 min read
Modern CSS Carousels: No JavaScript Required

Modern CSS carousels: No JavaScript required

This article walks through new CSS features like ::scroll-button() and ::scroll-marker() that make it possible to build fully functional CSS-only carousels.

Saleh Mubashar
Jun 6, 2025 ⋅ 5 min read
hidden coast of developer elitism

It’s time to break the cycle of developer elitism

Let’s talk about one of the greatest problems in software development: nascent developers bouncing off grouchy superiors into the arms of AI.

Lewis Cianci
Jun 4, 2025 ⋅ 9 min read
When To Use Flexbox And When To Use CSS Grid

When to use Flexbox and when to use CSS Grid

Flexbox and Grid are the heart of modern CSS layouts. Learn when to use each and how they help build flexible, responsive web designs — no more hacks or guesswork.

Leonardo Maldonado
Jun 3, 2025 ⋅ 9 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