Today is Sunday.
Before starting a new week, I decided to close this one properly.
Usually, I write my weekly posts on Monday or Tuesday. The reason is simple: most sections in this course take more than one week, and sometimes a few concepts are still left to explore or refine.
But this time, things felt different.
The useReducer section finished faster than I expected.
So instead of dragging it into next week, I decided to end Week 16 today and start Week 17 fresh with a new section and a new mindset.
This Week Was All About useReducer (For Real)
The main focus of this week was useReducer.
Not just learning what it is — but actually using it properly.
Over the last two blogs, I already shared the full journey:
- First, I built a real React Quiz application using useReducer
- Then I practiced with a Bank Account challenge
- I also worked with a fake API (json-server) to make things more realistic
This week taught me something very important:
useReducer is not about replacing useState.
It is about controlling workflows, rules, and complex state transitions.
I finally stopped thinking in “variables” and started thinking in states and actions.
What I Really Learned This Week
This week was not about quantity. It was about depth.
I learned:
- How to design state like a state machine
- How to centralize logic instead of spreading it across components
- How real apps think in transitions, not just values
- Why useReducer feels like modern React with classic architecture thinking
And most importantly:
Some weeks are not about learning new things.
Some weeks are about understanding something properly.
This was one of those weeks.
Closing Week 16, Starting Week 17
This section is now complete.
- useReducer ✅
- One real app ✅
- One challenge ✅
- Fake API integration ✅
It feels good to close this chapter cleanly.
Tomorrow, I start Week 17 and a new section with a fresh mind and new goals.
Top comments (0)