Your example doesn't actually comply with the redux Duck spec. #5

In the rules section located here you'll notice that a duck: MUST have action types in the form npm-module-or-app/reducer/ACTION_TYPE

Your action types arn't using the proper namespace of appname/reducer. That part is extremely important to avoid name collisions in other reducers. IE. I sometimes have the same action type names in different reducers but they don't collide due to the namespacing.

I would recommend changing that in the example code since you link people to it in your medium comment. :-)

Great article though and glad you're giving this pattern awareness in the community! I think it's super important