@Tech_Next_Gen profile picture
Kritik @Tech_Next_Gen

React • Next.js • Full-Stack Engineering - Clean code, real problems, practical solutions

Joined August 2022
  • Tweets 3,057
  • Following 703
  • Followers 756
25 Photos and videos
Pinned Tweet
Kritik@Tech_Next_Gen
3 Nov 2025
Every time you type, your React component re-renders 50 times. You probably don't even know it's happening. Common mistake: ❌ Bad:
7
14
2,050
Kritik@Tech_Next_Gen
19 Nov 2025
The most expensive bugs aren’t caused by bad code. They’re caused by code that looked “too safe to fail.” Assumptions create bugs. Verification removes them. What’s the costliest assumption you’ve seen in production? 👇
4
139
Kritik@Tech_Next_Gen
19 Nov 2025
The biggest difference between junior and senior devs? Seniors design for failure first Anyone can handle the happy path Real engineers handle: • timeouts • stale caches • broken JSON • nulls • slow DB queries Think about failure → build systems that survive. Thoughts? 👇
1
4
292
Kritik@Tech_Next_Gen
17 Nov 2025
React pattern I learned WAY too late: Early returns instead of nested ifs. Here's the messy way I used to do it
3
4
455
more replies
Kritik@Tech_Next_Gen
17 Nov 2025
Pro tip: Handle edge cases first. Return the main UI last. Your code flows top-to-bottom. Your brain reads top-to-bottom. Match them.
1
3
113
Kritik@Tech_Next_Gen
17 Nov 2025
Every React dev should know this pattern. I use it in every component now. What's YOUR go-to for clean conditional rendering? 👇 Save this as your reference 🔖
3
102
Kritik@Tech_Next_Gen
13 Nov 2025
When do you refactor your code? Here's my controversial take 👇
1
5
205
Kritik@Tech_Next_Gen
12 Nov 2025
Your React app feels slow — but it's not React's fault. Before you blame the framework, check for these 👇 ☐ Functions created inside JSX ☐ Inline objects/arrays as props ☐ Missing React.memo ☐ Missing useCallback ☐ Broken useEffect deps 3 more below 👇
4
5
224
Kritik@Tech_Next_Gen
12 Nov 2025
☐ Using index as key ☐ State causing cascading re-renders ☐ Mutating state directly Fix all 8 in order — your app will fly. Bookmark this. Next time you profile, you'll know where to look. 🔖
3
119
Kritik@Tech_Next_Gen
11 Nov 2025
I built a perfect signup form. Fast, flawless, bug-free. Then I watched a real user try it. Three password errors. They quit. My code worked. My design failed. Good code solves your problem. Great code solves theirs. We build experiences, not features. Ever happened? 👇
3
10
321
Kritik@Tech_Next_Gen
10 Nov 2025
Stop using index as key in React. It works — until it silently breaks your UI. Here's why this causes weird re-renders 👇
4
7
390
more replies
Kritik@Tech_Next_Gen
10 Nov 2025
✅ The fix: Use unique IDs instead of index. items.map(item => ( <div key={item.id}>{item.name}</div> )) React tracks each item by ID — not position. Delete, filter, or reorder → no glitches.
1
5
133
Kritik@Tech_Next_Gen
10 Nov 2025
The rule: ⚠️ key={index} → works today, breaks tomorrow ✅ key={item.id} → stable forever Index keys only work for static lists with no state. Save this thread 💾 You’ll thank yourself when your UI stops glitching. Ever shipped this bug? 👇
4
98
Sunday morning reality check: Your code works. You don't know why. You're scared to touch it. "If it works, don't fix it." And that's how legacy code is born. Every project has that one mysterious file. Been there? 👇
3
117
Your component won’t re-render even though the state changed. You push, splice, or update the array Console shows the change. UI frozen. React checks references, not contents. Mutating state = invisible updates. Fix: always create a new array reference. Ever panic over this?
3
6
1,226
Load more