👋 Hey Twitter! I’m starting my #100DaysOfFullStack challenge 🚀 Goal: Learn Next.js, build SaaS apps, and share everything I learn in public. If you’re also learning or building — let’s connect 👇 #Nextjs #BuildInPublic #CodingJourney

Learning coding be like: Step 1: I understand. Step 2: I don’t. Step 3: I understand again. Step 4: I don’t again. And repeat forever 🔁😂 #codingjourney #buildinpublic #100daysofcode

Added PostHog to my Next.js project ✅ •User flows tracked Visualizing real usage in my current project. It hits different when the data isn’t a guess anymore. It also has mcp servers can wait to try it out #buildinpublic #nextjs

Today’s DSA: 26. Remove Duplicates from Sorted Array Key things: You don’t remove anything. You just *overwrite* while tracking the position of the last unique element. Intuition: • One pointer (r) walks through the array • The second pointer (l) marks the position to place the

Some days progress is just: → Open laptop → Touch the project → Move 1% forward 1% compounds.

AI se darr kyu? Hum toh woh log hain jo YouTube se engineering kar le. #AI

✨ Built a reusable constants.ts file with real data today with the help of GitHub Copilot — and used it to render multiple events with an EventCard component in Next.js 16. It feels good when the project starts becoming structured 🔥 Key lesson: Keep your data separate from your

💡 Key Takeaways • Start with a simple approach, then optimize • Hash maps = instant lookups • Time complexity thinking makes you a better coder #Python #LeetCode #CodingJourney #TwoSum #100DaysOfCode

⚡ Optimized Approach (O(n)) Use a hash map to store numbers and their indices as you go 💥 Finds the pair in one pass!

🧩 Brute Force Approach (O(n²)) Check every pair until you find two numbers that add up to the target ✅ Simple ⚠️ Slow for large lists

Solved the classic Two Sum problem on #LeetCode today — one of the best exercises to learn how to move from brute force ➜ optimized thinking. Here’s the breakdown 👇

🔥Building Next.js From Scratch (While Watching YouTube) Installed Next.js 16, Tailwind CSS, and Shadcn. First lesson: 90% of building is just getting your dev environment to cooperate 😂” #BuildInPublic #Nextjs #WebDevJourney #CodingInPublic

“AI won’t replace humans. Humans using AI will replace humans who don’t.” Every Team/Individual has AI in their future RoadMap and you should too! #AI #FutureOfWork

5️⃣ Real-World Use Case Imagine your dashboard data fetch fails temporarily. Instead of a blank screen, you show: “⚠️ Something went wrong — Try again. ”That’s a pro-grade user experience 🚀

4️⃣ How It Works When an error happens inside a route: 1️⃣ Next.js catches it 2️⃣ Stops it from crashing everything 3️⃣ Renders your error.js instead→ Smooth recovery, no white screen of death 👻

3️⃣ Basic Error File Example // app/dashboard/error.js 'use client'; export default function Error({ error, reset }) { return ( <div> <h2>⚠️ Something went wrong!</h2> <p>{error.message}</p> <button onClick={() => reset()}>Try again</button> </div>

2️⃣ The Setup 📁 Folder example: app/ ┣ dashboard/ ┃ ┣ page.js ┃ ┗ error.js ┗ layout.js ✅ If something fails in /dashboard/page.js, Next.js auto-shows error.js.

1️⃣ The Problem Before, if a page crashed — 💣 whole app crashed. Now with the error.js file in the App Router, each route has its own safety net. Think of it like: 🧱 Each section of your app has a personal “crash cushion.”

🧵 Error Handling in Next.js — Explained Simply ⚠️ Just learned how the error.js file works in #Nextjs 16, and it’s a game changer for catching page crashes without breaking the whole app 💥 Here’s how it works 👇 #React #Nextjs #100DaysOfFullStack

Final Thought Route Groups are like folders with invisibility cloaks 🪄 — super useful when your app grows.Organize better. Deploy cleaner. Code happier 😎#Nextjs #React #FullStack