Are you talking to me?

Awesome addition to the web

You're not self-taught. No one is. Every step, every skill comes from Mentors, Books, Courses, even Failure, and your Community. Own your influences, celebrate your growth! #LearningInPublic #BuildInPublic #GlobalStack

Optimize DB Queries FIRST. Cache SECOND. Optimized DB queries are your foundation. They'll give you better latency improvements than simply caching everything. Focus on cache invalidation logic—that's the hardest and the most important. Cache only frequently accessed data.

Do NOT use microservices to justify microfrontends. While microservices make sense when needed, microfrontends are usually never needed and very slow and introduce complexity, architectural burdens, synchronisation problems, and more cost.

AI Or DSA ?

I just finished an interview with an AI. Where I explained code and architecture. Considering cutting costs and filtering applicants, I think using AI to conduct interviews rather than DSA platforms should be the future. AI proctored interviews Or DSA proctored screenings

How unstable props break memoization #buildinpublic

Unstable props like functions and objects are silent memo-killers. Your memoized components? Might as well be regular ones. 📌 That’s Part 1. Part 2 drops soon → follow @GlobalStackdev for deeper React gotchas. #ReactJS #buildinpublic

⚠️ Your React.memo isn’t broken. But it's not working either. Unstable props can quietly kill memoization — and your performance.

Honest Question It's a fact that building in public helps increase visibility. Aside from talking about what you are building on X. What other activities are considered building in public that actually helps to achieve the benefits of building in public? #buildinpublic

Can someone please list the possible reasons why a github account might be suspended? What are the possible ways one can sync and backup codes hosted on github? #buildinpublic a day at a time.

More possible fixes ⚙️ #REACT #reactnative

The Fix 🔨

It's a simple bug with heavy consequences. On every render, interests is assigned to a new array when user is null. The Effect runs and updates some states, react re-renders, the interests variable is assigned a new array, effect runs again, react re-renders and hence the loop 🔁

React is fast — until a tiny useEffect bug brings it to its knees. This code is a sample representation of what we had in prod. The genesis of the bug.

Would you call this skill Issue? How one of our React components had a subtle performance issue in production. Logged-out users triggered endless re-renders. The UI didn't crash — but it was clearly struggling. 🧵👇

🛠️ Possible Fixes: Create a custom usePosts hook that caches and returns a stable reference: #react #reactnative

⚠️ Subtle Danger: Using derived state (posts) inside a useEffect() dependency:

✅ A Better Approach: Use derived state with a custom hook.