Well, bear in mind that partly, it was horrific because I was new to it, and it was very much in at the deep end. * inconsistently named action creators define

Well, bear in mind that partly, it was horrific because I was new to it, and it was very much in at the deep end. * inconsistently named action creators defined in the same file(sometimes) as the actions * confusing tests that I still don't understand * the main focus being on axios requests handled in reducers rather than reducers themselves * the two main reducers being updateData (which merged in object into the store and saveData which fired off the axios request, and every component had to implement custom logic around using these two. Connects everywhere (which a child comment warns against!) Don't think anyone working on it had made any one decision badly - just a combination of using a new tech in a slightly non standard setting, deadlines, and a strange backend integration. Also, I don't think any of it was Redux's fault. That link looks good, thank you, will try it out and see if it is similar to what I came up with on my own for this new project. Edited for spacing