Even on packed days, doing something small keeps the learning energy flowing ⚡

The project’s still in progress, but I’m proud of every step forward 🚀

x.com/abhishekgo49...

🎬 Worked on a Movie Search App UI today — focused only on the design (no logic yet).

Practiced:
• Clean React component structure
• CSS styling for a modern look
• Prepping to connect TMDb API soon 🔗

Status update ⏳

Weather data is fetching successfully, but UI integration is still in progress 🌡️💨
Not done yet, but learning is solid and confidence is growing 💪

One bug. One fix. One day at a time ✨

x.com/abhishekgo49...

What I learned today 👇

✍️ Handling input with useState
🖱️ Triggering API calls using onClick
🔗 Using template literals for dynamic API URLs
🐞 Debugging API errors step by step

UseEffect only returns a cleanup function, not data
Practised fetching data from an API and rendering it safely with the user.[0]?.name
Today’s takeaway:
React looks simple when you read it, but it reveals its smart layers only when you break something,
Small bugs, big lesson.

x.com/abhishekgo49...

Second win: fetching API data and showing it on the UI.

I learned how to:
• call an API on mount
• store the response in state
• render it dynamically
• avoid infinite loops
• understand how React re-renders when state changes
Seeing data appear on the UI in real time.

Learning React useEffect and making a Project
Live Clock App 🕒

I built a simple Clock App that updates every second — and in the process, I finally understood how useEffect really works.

x.com/abhishekgo49...

5️⃣ Core takeaway 💡

setState → re-render → React checks dependencies → maybe re-run effect.

Understand this cycle, and useEffect stops being confusing magic.

4️⃣ The infinite loop trap ⚠️

If your effect depends on count and updates count,
it re-renders forever.

That’s because the dependency keeps changing — so the effect never stops.

3️⃣ How state interacts with useEffect

Every time you call setState, React re-renders → then checks dependencies → and decides whether to re-run your effect.

That’s the core logic loop.

2️⃣ When does it run?
It runs after React finishes rendering your UI.
Timing depends on the dependency array:
[] → runs once on mount
[count] → runs whenever count changes

1️⃣ What is useEffect? It’s where you put your side effects — things that happen outside React’s normal rendering (like fetching data, setting timers, or updating the title).

Still learning. Still breaking things. Still fixing them. Back at it tomorrow 🚀

x.com/abhishekgo49...

Every time you type in an input, onChange fires.

And event.target.value is literally the latest character you just typed.

Simple… but powerful.

Abhishek Goud
@abhishekgo49196
·
Dec 9
Some parts are still foggy, and that’s okay.
I’ll revisit, rebuild, and make it sharp.
Consistency > confidence.
Day 10 loading… 🚀

x.com/abhishekgo49...

Big learnings today:

• Controlled inputs
• Correct array state updates
• map() for UI
• Why direct state mutation breaks apps

Also learned that confusion is not failure, it’s the doorway 🚪

x.com/abhishekgo49...

I built a simple counter component 💻 Fixing state logic step by step really helped!

React is becoming clearer bit by bit.
Excited for tomorrow’s concept! 🚀

x.com/abhishekgo49...

Key takeaways:
• State gives components memory 🧠
• Always use the setter to update state 🔄 (direct variables won’t re-render UI)
• Use previous state when needed: setCount(prev => prev + 1) ⏮️
• Event handlers need careful parameter passing ⚠️

x.com/abhishekgo49...