Tech_Next_Gen's profile picture. Full Stack Developer | Web, Backend & System Design

Real-world lessons from bugs, builds & scalable systems

Kritik

@Tech_Next_Gen

Full Stack Developer | Web, Backend & System Design Real-world lessons from bugs, builds & scalable systems

고정된 트윗

Every time you type, your React component re-renders 50 times. You probably don't even know it's happening. Common mistake: ❌ Bad:

Tech_Next_Gen's tweet image. Every time you type, your React component re-renders 50 times.

You probably don't even know it's happening.

Common mistake:

❌ Bad:

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?

Tech_Next_Gen's tweet image. 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?

A frontend sent a request. The backend waited. And waited. The dev blamed the server. But it was fine. The real bug? Forgot to await. The code ran. UI rendered without data. Added one word: await. Fixed. Tiny mistakes. Huge panic. Ever had a missing await scare?


90% of slow Next.js apps can be fixed with 3 checks - 1. Image optimization (next/image) 2. Dynamic imports (lazy loading) 3. Database query count (N+1 problem) Fix these first — then think caching or RSCs. What slowed down your app?

Tech_Next_Gen's tweet image. 90% of slow Next.js apps can be fixed with 3 checks -

1. Image optimization (next/image)
2. Dynamic imports (lazy loading)
3. Database query count (N+1 problem)

Fix these first — then think caching or RSCs.

What slowed down your app?

Kritik 님이 재게시함

Why is your API making 100+ database calls when it needs 1? 100 users = 101 database calls. 3 seconds per request. It's called the N+1 query problem. Most developers don't even know it's happening. Full breakdown in my reply below 👇


Unpopular opinion: Framework tutorials make you worse at JavaScript. You can build features in React. But when you see "Cannot read property of undefined" you have no idea where to start. Learn the language first. Framework is just a tool. Agree or disagree?

Tech_Next_Gen's tweet image. Unpopular opinion:

Framework tutorials make you worse at JavaScript.

You can build features in React.
But when you see "Cannot read property of undefined" you have no idea where to start.

Learn the language first. Framework is just a tool.

Agree or disagree?

Yet another Chromium fork — but this one claims to be different. Thoughts?

Open-source Agentic browser; privacy-first alternative to ChatGPT Atlas, Perplexity Comet, Dia.

GithubProjects's tweet image. Open-source Agentic browser; privacy-first alternative to ChatGPT Atlas, Perplexity Comet, Dia.


These 4 "rules" are actually slowing you down: 1. "You need a CS degree" → You need portfolio projects 2. "Learn all frameworks" → Master one deeply 3. "Perfect code before shipping" → Done > perfect 4. "Never copy code" → Understanding copies = learning Did I miss any?


Honest Saturday morning status: Coffee: 2 cups in ☕ Code written: 0 lines Browser tabs: 21 open Times checked X: Don't ask Motivation: TBD But that's okay. Not every Saturday needs to be productive. Sometimes it's just opening VS Code & vibing. What's your Saturday vibe? 👇


Hot take: ChatGPT is making junior developers WORSE, not better. They copy the code. They paste it in their project. It works. They learn nothing. Then they can't debug when it breaks. AI is a tool for people who already know how to code. Not a shortcut for people who don't.


Loading...

Something went wrong.


Something went wrong.