Joined November 2024
- Tweets 138
- Following 43
- Followers 10
- Likes 22
16 Photos and videos
π‘ Day 80/100
80 days into this challenge π
Biggest lesson so far?
Consistency compounds.
Small progress daily > random motivation.
#100DaysOfCode #Frontend #ReactJS
3
π‘ Day 79/100
React Tip: Use environment variables
β hardcoded API keys
β
.env files
Cleaner safer setup.
#100DaysOfCode #ReactJS #Frontend
6
π‘ Day 78/100
React taught me this:
Most React problems are actually JavaScript problems.
Strong JS fundamentals make React WAY easier.
#100DaysOfCode #ReactJS #JavaScript
3
π‘ Day 77/100
React Tip: Create reusable layouts
Layouts are components too.
Cleaner structure.
Less repeated code.
#100DaysOfCode #ReactJS #Frontend
3
Jun 7
π‘ Day 73/100
React Tip: Prevent unnecessary re-renders
β
useMemo()
β recalculating every render
Performance matters in larger apps.
#100DaysOfCode #ReactJS #Frontend
7
Jun 6
π‘ Day 72/100
The moment React components βclickedβ for meβ¦
Frontend development started feeling WAY more scalable.
Write once.
Reuse everywhere.
#100DaysOfCode #ReactJS #Frontend
8
Jun 5
π‘ Day 71/100
React Tip: Use optional chaining
β
user?.profile?.name
β user.profile.name
Safer rendering for async data.
#100DaysOfCode #ReactJS #Frontend
3
Jun 5
π‘ Day 70/100
React Tip: Use controlled inputs
β
value onChange
β uncontrolled forms
Predictable forms = better React apps.
#100DaysOfCode #ReactJS #Frontend
2
Jun 3
π‘ Day 69/100
React taught me something important:
Frontend is more about THINKING than typing.
Planning components properly saves hours later.
#100DaysOfCode #ReactJS #Frontend
2
Jun 2
π‘ Day 68/100
React Tip: Avoid using index as key
β key={index}
β
key={item.id}
Stable keys = fewer UI bugs.
#100DaysOfCode #ReactJS #Frontend
1
8
Jun 1
π‘ Day 67/100
React Tip: Use loading states
β
Loading...
β blank UI during fetches
Better UX fewer errors.
#100DaysOfCode #ReactJS #Frontend
1
8
May 31
π‘ Day 66/100
Beginner React:
One component doing EVERYTHING π
Now:
- smaller files
- reusable components
- cleaner structure
Large components become a nightmare fast.
#100DaysOfCode #ReactJS #Frontend
1
12
May 30
π‘ Day 65/100
React Tip: Keep state minimal
β duplicate state
β
derive values when needed
Less state = fewer bugs.
#100DaysOfCode #ReactJS #Frontend
9
May 29
π‘ Day 64/100
React Tip: Use conditional rendering
β
{isLoggedIn && <Dashboard />}
β hiding with CSS
If it shouldnβt exist, donβt render it.
#100DaysOfCode #ReactJS #Frontend
1
2
197
May 28
π‘ Day 63/100
React once told me:
βObjects are not valid as a React childβ π
Problem?
I rendered:
{user}
Instead of:
{user.name}
That error confused me for HOURS.
#100DaysOfCode #ReactJS #Frontend
1
8
May 27
π‘ Day 62/100
React Tip: Donβt overuse useEffect
Sometimes:
β
plain JS
is better than:
β extra state effects
Keep components simple.
#100DaysOfCode #ReactJS #Frontend
1
6
May 26
π‘ Day 61/100
React Tip: Destructure props
β
function Card({ title })
β props.title everywhere
Cleaner & easier to read.
#100DaysOfCode #ReactJS #Frontend
1
May 25
π‘ Day 60/100
Before React my file names were like:
appFINALfinal2.js π
React forced me to improve:
- structure
- organization
- scalability
It changed how I build projects completely.
#100DaysOfCode #ReactJS #Frontend
1
23
May 24
π‘ Day 59/100
React Tip: Use functional updates
β
setCount(prev => prev 1)
Why?
- Prevents stale state bugs
- Safer async updates
#100DaysOfCode #ReactJS #Frontend
8