For the past few days, I have been slowly starting to explore Redux while continuing work on my side project.
I didn't build anything big today, but I did something that is just as important: understanding architecture and improving project structure.
Sometimes development progress is not about adding new features — it's about organizing and understanding the code better.
Beginning to Understand Redux
Today I started learning Redux and the first thing that caught my attention was how similar Redux feels to React’s useReducer hook.
Because I already spent time learning useReducer, Redux concepts started to make more sense.
Both follow a similar pattern:
- a state
- a reducer function
- actions that describe changes
- updates handled in a predictable way
Redux simply expands this idea for global state management across the application.
Right now, I am still in the early stages and trying to understand the overall flow.
Practicing Redux with a Small Project
To practice Redux concepts, I started working on a small learning project called:
The React Redux Bank
The goal of this project is to understand how Redux manages:
- actions
- reducers
- dispatching updates
- global state flow
Instead of just reading theory, I prefer learning by building small projects and experimenting.
This project will help me understand Redux step by step.
Improvements in My Side Project
Alongside learning Redux, I also worked on my side project.
The focus today was not optimization or adding new functionality.
Instead, I worked on refactoring the structure of the appointment booking section.
This booking flow includes several steps such as:
- selecting a service
- choosing a date
- selecting staff
- and other booking steps
Previously, these parts were written together in a single structure.
Today I started breaking them into separate components.
After separating the components, I wired them back together so they render correctly in the application.
The structure is still not fully finalized, and there is no optimization yet. For now, the goal is simply to build a clean component architecture first.
Why Structure Matters
While building projects, it is tempting to focus only on features.
But as projects grow, structure becomes extremely important.
Breaking features into smaller components helps with:
- readability
- maintainability
- scalability
- easier debugging
This step might not be visible to users, but it makes the codebase much healthier.
Honest Learning Progress
Not every development day is about building something impressive.
Some days are about:
- understanding new concepts
- restructuring existing code
- improving project organization
- experimenting with new tools
Today was one of those days.
And honestly, these days often teach the most.
What I'm Doing Next
My next goals are:
- continue learning Redux concepts
- complete the React Redux Bank practice project
- finalize the component structure of my side project
- start improving performance and optimization
Step by step, the goal is to become more confident with state management and scalable React architecture.
If you're learning React or Redux too, feel free to share how you're approaching it. I'd love to hear different learning strategies.
Top comments (0)