
Why use redux? structured approach to state management, separation of concerns, inferred types, use vanilla createReducers and/or createSlices all together
Software Engineer
I am a software engineer, with a creative mindset. My passion for learning has motivated me to stay curious, to continuously search out new technologies leading me to many interesting problem spaces. I have worked with teams locally and around the world on solutions for organizations in government, civil construction, non for profit, prop-tech and agri-tech. I have studied at the Queensland University of Technology, The University of Queensland and University of the Sunshine Coast. My interests are developing solutions for the front-end finding robust elegant solutions for complex business requirements and using data to help build the right solution. I have fun going on epic camping adventures, Hiking, sitting by an open fire, I also have a temperamental interest in learning the fine art of cartography.
Markdown supported · ⌘↵ to post
ant sam
Sorry, but you didn'd help me sleep easier :(
How redux slices follow Dependency Inversion Principle? Vanilla Redux have abstraction in actions and implementation in reducers. But slice contains actions and concrete implementation in a one file.