---
title: "Stephan Meijer (@smeijer) | Hashnode"
description: "Stephan Meijer (@smeijer) writes on Hashnode. Read their latest articles and follow their work."
url: "https://hashnode.com/@smeijer"
---

@smeijer

# Stephan Meijer

@smeijer · Joined November 2016

## Comments

[Yes it's mine. I should have mentioned that. I use it with redux-actions and redux-saga like the example in the readme. And really like the now obvious separation between actions and status updates. While having less boilerplate.](https://hashnode.com/posts/tips-for-a-better-redux-architecture-lessons-for-enterprise-scale/58327eec23b26d367bf71cd3/comment/58331a82d30fa81b7b8a270a#reply-5833209fa96be26a2dc48f91)

Reply · Article · Nov 21, 2016 · 2 · [Tips For a Better Redux Architecture: Lessons for Enterprise Scale](https://hashnode.com/posts/tips-for-a-better-redux-architecture-lessons-for-enterprise-scale/58327eec23b26d367bf71cd3)

[If you were using redux-define you could reduce the boilerplate of defining action types. Especially when using status suffixes like ERROR or SUCCESS, it can make a big difference. Turning your example export const ADD\_TODO = 'todos/ADD\_TODO' export const ADD\_TODO\_SUCCESS = 'todos/ADD\_TODO\_SUCCESS' export const ADD\_TODO\_FAILURE = 'todos/ADD\_TODO\_FAILURE' Into export const ADD\_TODO = defineAction('ADD\_TODO', \[SUCCESS, FAILURE\], 'todos');](https://hashnode.com/posts/tips-for-a-better-redux-architecture-lessons-for-enterprise-scale/58327eec23b26d367bf71cd3/comment/58331a82d30fa81b7b8a270a)

Comment · Article · Nov 21, 2016 · 8 · [Tips For a Better Redux Architecture: Lessons for Enterprise Scale](https://hashnode.com/posts/tips-for-a-better-redux-architecture-lessons-for-enterprise-scale/58327eec23b26d367bf71cd3)