DEV Community: Ogundare Toluwase Enoch

Why So Many Ways to Manage State in React? 🤔

Ogundare Toluwase Enoch — Thu, 11 Sep 2025 10:00:24 +0000

Last year, when I started React, I entered the world of state management.

At first, it was simple.

I used props:

It felt so smooth to just pass data around — until it started becoming overwhelming.

Then I discovered useState:

Wow! A hook that could manage state directly. I thought, “This is it! I’ve mastered state management.”

But React wasn’t done with me.

Soon, I met useContext:

I still remember my reaction that day:
“React, can’t you just focus on one and let me continue my thing?” 😂

Then came useReducer:

It introduced structure, but at the same time I was like:
“Just kill me React!!!”

And finally, I reached Redux, the one I kept hearing about everywhere:

A central storage for handling complex applications.

Looking back, I thank God for the progress 🙏.

Yes, they’re all about state management. But each has its limitations, and each comes into play as apps (and developers) grow.

That opened my eyes to a bigger lesson:

➡️ The way we manage our state in life last year may not be enough for this year.

➡️ Growth brings more complexity, more responsibility… and sometimes, more stress.

But with the Lord, it becomes ease.

Someone once told me:

“When you are succeeding, running, and pushing — it’s race. But when God is beside you — it’s grace.”

Today, even though I’m not yet where I expect to be, when I look back at previous years and how I managed “state” in life then versus now, I see it’s been God’s grace all along. ✨

🔥 Props → useState → useContext → useReducer → Redux

💡 React taught me state management. God is teaching me life management.

👉 How about you? Which state management tool gave you the biggest “aha” or “stress” moment when learning React?

Why TypeScript, if JavaScript can do it all? 🤔

Ogundare Toluwase Enoch — Thu, 11 Sep 2025 08:41:16 +0000

Recently, I was chatting with a friend about TypeScript vs JavaScript.

She laughed and said:

👉 “TypeScript is like the elder brother of JavaScript.”

At first, I laughed too 😂, but then it hit me — that’s actually true!

Think about it:

An elder brother is usually protective and a bit strict.
JavaScript is free-spirited and flexible (sometimes too flexible).

TypeScript steps in as the elder brother, keeping things in check with strict typing and rules.

Just like an elder brother might say:

“Don’t do that, you’ll get hurt!”

TypeScript tells JavaScript:

“Don’t pass a string where a number should be, you’ll break things!”

So why TypeScript if JavaScript can do it all?

✔️ Catch errors early — mistakes are spotted during development, not when your app is live.

✔️ Better tooling — autocomplete, hints, and refactoring feel magical.

✔️ Scales with teams — large projects are easier to maintain and collaborate on.

✔️ Safer code — your app runs with fewer surprises.

Example:

JavaScript

TypeScript

The truth is…

JavaScript can do it all.

But TypeScript helps you do it all with confidence — like an elder brother making sure you don’t get into trouble.

So yeah… elder brothers, keep being strict with your younger ones 😅. It really helps!

The Dev Journey

Ogundare Toluwase Enoch — Tue, 09 Sep 2025 15:19:06 +0000

Hi everyone 👋,

My name is Ogundare Toluwase Enoch, and I’m a Frontend Developer passionate about building clean, user-friendly applications with React and Tailwind CSS.

A few days ago, my uncle encouraged me to start showcasing my skills and connecting with others in the field for lessons and experience. That small push inspired me to start sharing my journey more openly.

Over the past few years, I’ve built several projects with React and Tailwind, sharpening my frontend skills. Recently, I decided to take the leap into backend development with the goal of becoming a full-stack developer 🚀.

I’ll be sharing my journey here: the wins, the struggles, and everything in between. I’d also love to learn from those ahead of me while connecting with fellow learners.