Sohail Khan’s Post

If this post found you, take it as your sign to build something small this week. You don’t need a perfect idea or a big plan. What matters is getting started with a stack you can set up quickly. How I’d start a side project in the end of 2025: - Pick a problem you actually have - Cut the scope to what fits in 10 days - Use tools you already know - Build one vertical slice end to end - Ship it publicly Two simple paths: 💡 Frontend-only (fastest to ship) - Vite + React - Tailwind or plain CSS - Local JSON or MockAPI - Deploy on Vercel or Netlify ⚙️ Full-stack (when you need auth or data) - Next.js (App Router) - Auth.js or Clerk - Drizzle ORM + Postgres (Neon or Supabase) - Deploy on Vercel, add Cron if needed First milestone ideas: - One item added and saved - One full flow works end to end - One clear result displayed - App live and working The goal isn’t perfection. The goal is to finish something real you can click, test, or share by next week. 👉 What would you build if you gave yourself 10 focused days? #webdev #fullstack #frontend #sideproject #softwareengineering

🎯#90DaysOfCode Challenge | Day 12/90 Ever get stuck deciding what to cook? 🧑🍳 For Day 12 of my journey to MERN stack, I built something to help: a Recipe Finder App using Html & Css and JavaScript, pulling live data from TheMealDB API. ➖This project was a major step up! It forced me to move beyond static pages and learn how to interact with the wider web to bring dynamic content into my application. ➖Key skills sharpened with this project: 🌐 Mastering API Integration: This was my first time connecting to a live, external API. I practiced using fetch with async/await to send requests, handle responses, and parse JSON data – a fundamental skill for any web developer. 💡 Handling Asynchronous Operations: Truly understanding async/await was crucial. Making the app wait for recipe data before updating the UI prevents errors and creates a smoother experience. ✨ Dynamic HTML Generation: I wrote JavaScript to take the raw API data and transform it into a user-friendly display, including search results, detailed recipe instructions, ingredient lists, and even embedded YouTube videos. 🚦 Robust Error Handling & UI States: Implemented logic to gracefully handle cases where no recipes were found for a search term, providing clear feedback instead of a blank screen. Working with real-world APIs like this in vanilla JS builds a strong foundation for connecting React frontend to backend API's in the MERN Stack. It’s exciting to see data flow! 🌐Live Demo: https://lnkd.in/g8_MTMm8 #90DaysOfCode #JourneyToFullStack #WebDevelopment #Frontend #JavaScript #API #AsyncAwait #FetchAPI #VanillaJS #CodingChallenge #Day12

I once opened a project I had built months earlier. It ran fine, but I couldn’t understand a single thing. Variables named data1, temp, and something. Functions are stacked on top of each other like a pile of dishes. It worked… but it wasn’t clean. It dawned on me: The mess wasn’t just in my code, it was in my head. I had been rushing and trying to “just make it work.” But clean code doesn’t come from chaos. It comes from calm. When your mind is scattered, your code will be too. But when you slow down, think clearly, and name things with purpose, you’re not just writing better code, you’re building better focus. Clean code isn’t only a technical skill. It’s a reflection of how you think. So the next time you refactor, don’t just clean your functions, clean your mind too. Step back. Breathe. Then write again with clarity. What’s one habit that helps you write cleaner, more intentional code? #CleanCode #SoftwareDevelopment #WebDevelopment #NextJS #ReactJS #JavaScript #FrontendDevelopment #CodingMindset #Developers #TechCommunity

🚀 DAY 6 POST — “The Most Underrated Full-Stack Skill: State Management” Everyone talks about frameworks. No one talks about the thing that actually keeps your app alive: state management. Whether it's React, Node, Redux, Context, MongoDB, or even localStorage — the biggest challenge in full-stack development isn’t writing code… It’s maintaining predictable state across your entire system. Here’s what experience taught me: 🔹 UI breaks? → Usually state. 🔹 API glitch? → Wrong state flow. 🔹 Lagging page? → Over-rendering because of state. Full-stack development becomes 10x smoother when you understand how to manage data flow cleanly. 💡 Great developers don’t just write code. They control state. What do you prefer for state handling? Redux? Context? Zustand? Jotai? Or good old props? 👇 #MERN #FullStack #ReactJS #StateManagement #WebDevelopment #JavaScript #TechCommunity #Frontend

🎯 𝗠𝗮𝘀𝘁𝗲𝗿 𝗝𝗮𝘃𝗮𝗦𝗰𝗿𝗶𝗽𝘁 𝘄𝗶𝘁𝗵 𝗧𝗵𝗶𝘀 𝗨𝗹𝘁𝗶𝗺𝗮𝘁𝗲 𝗖𝗵𝗲𝗮𝘁 𝗦𝗵𝗲𝗲𝘁! If you want to level up your JavaScript skills, this comprehensive JavaScript Cheat Sheet is the perfect quick reference for developers at any stage — beginner to advanced. 💡 𝗪𝗵𝘆 𝗬𝗼𝘂’𝗹𝗹 𝗟𝗼𝘃𝗲 𝗧𝗵𝗶𝘀 𝗖𝗵𝗲𝗮𝘁 𝗦𝗵𝗲𝗲𝘁: This guide brings together all the essential syntax, concepts, and best practices to help you write cleaner, faster, and more efficient code. It’s designed to save time, enhance productivity, and simplify problem-solving in real-world projects. ⚙️ 𝗪𝗵𝗮𝘁’𝘀 𝗜𝗻𝘀𝗶𝗱𝗲: ✅ Core Concepts – Variables, data types, operators, and control structures ✅ Functions – Arrow functions, higher-order functions, and callbacks ✅ Objects & Arrays – Destructuring, spreading, and deep copying ✅ ES6+ Features – Let/const, template literals, modules, and classes ✅ Asynchronous JS – Promises, async/await, and event loop explained ✅ DOM Manipulation – Querying, events, and dynamic UI updates ✅ Error Handling – Try/catch, custom errors, and debugging tips ✅ Interview Essentials – Closures, hoisting, prototypes, and this keyword 🚀 Whether you’re building with React, Node.js, or working on MERN stack projects, this cheat sheet will help you code smarter and faster. credit 🫡 👉 Sushant Desai #JavaScript #MERN #ReactJS #NodeJS #TypeScript #MongoDB #WebDevelopment #SoftwareEngineering #TechInterview #Coding

💻 Day 3 of My 30-Day Backend Development & Coding Journey 🚀 Today was all about making my backend come alive visually — I learned how to connect server-side logic with dynamic HTML pages using EJS (Embedded JavaScript Templates) ⚙️💡 It’s amazing how templating helps render data dynamically — instead of sending plain text responses, I can now serve pages that update with real data 🤩 🧠 Topics I Covered Today: 🔹 What is Templating? — A way to generate dynamic HTML using logic and variables 🧩 🔹 Using EJS — The most popular templating engine for Express.js 💻 🔹 Views Directory — Where all .ejs templates are stored 📂 🔹 Interpolation Syntax — <%= %> to embed variables directly into HTML 🧠 🔹 Passing Data to EJS — Sending data from the backend to the frontend using res.render() Each day I’m realizing — backend development isn’t just about servers and APIs, it’s also about how data flows beautifully to the frontend 🖥️ Tomorrow I’ll explore partials, layouts, and reusability in EJS to write cleaner code 💪 #Day3 #30DaysOfCode #BackendDevelopment #NodeJS #EJS #ExpressJS #LearningInPublic #CodingJourney #Developers #WebDevelopment

🚀 6 NestJS Fundamentals Every Junior Developer Should Know If you're starting with NestJS, here are 6 core concepts that will help you build scalable and clean backend applications. I’ve explained them in a simple way so even beginners can understand 👇 --- 1️⃣ Modules – The Building Blocks Modules help you organize your project feature-wise. Think of them as folders that group related code (controllers, services, etc.). --- 2️⃣ Controllers – Handle Incoming Requests Controllers receive API requests and return responses. They define your routes like /users, /auth/login, etc. --- 3️⃣ Services – Write Your Business Logic All heavy logic should go inside services. Controllers should stay light and call services only. --- 4️⃣ Dependency Injection – No Need for new NestJS automatically creates and provides objects where needed. It keeps your code cleaner and easier to test. --- 5️⃣ Providers – Anything You Can Inject Services, repositories, helpers, factories… If NestJS needs to inject it, it must be registered as a provider. --- 6️⃣ Pipes, Guards, Interceptors – NestJS Power Tools Pipes → Validate & transform data Guards → Handle authentication & authorization Interceptors → Modify requests/responses, logging, caching #Technology #BackendDevelopment #WebDevelopment #NestJS #TypeScript #FullStackDeveloper

“Frameworks come and go, focus on fundamentals.” We’ve all heard this sentence so many times… and yes, fundamentals matter. But here’s something I’ve learned as a Software Engineer Knowing only the language is not enough. You can be great at JavaScript, understand scopes, closures, the event loop all the core stuff. But when you sit down to build a real, scalable, maintainable product, pure language knowledge won’t carry you very far. That’s because projects don’t run on syntax they run on architecture. And architecture doesn’t magically come from “just knowing code.” You need patterns, structure, conventions, and ways to organize your logic. This is where frameworks actually help you grow. 1- Nest.js teaches you modular and layered architecture. 2- Next.js teaches you routing, rendering strategies, caching. 3- Laravel teaches you service containers, middleware pipelines, repos. 4- Django teaches you MVC + ORM discipline. These frameworks aren’t “just tools.” They’re practical guides to software design. They expose you to patterns like dependency injection, singletons, repositories, adapters, modules, things you won’t naturally invent by writing plain Node.js scripts. So yes… fundamentals matter. But frameworks shape your thinking. They teach you how to write clean, maintainable, and scalable code. Anyone can write code. Not everyone can build systems. And frameworks help bridge that gap. By the way, what’s your current tech stack? #SoftwareEngineering #WebDevelopment #Programming #Frameworks #Architecture #DesignPatterns #JavaScript #DeveloperLife #TechLeadership #FullStackDev

🔥 Ready to Master the Modern Backend? 🔥 I'm thrilled to announce the launch of our new NestJS Backend Development Workshop Series! If you're comfortable with JavaScript/Node.js and ready to build scalable, robust, and enterprise-grade APIs, this series is for you. NestJS, powered by **TypeScript**, brings the best of modular architecture to the Node.js world. In this hands-on series, we'll cover the essentials and beyond: - W1: Foundation Setting up NestJS, understanding the core structure (Modules, Controllers, Providers).     - W2: Data Flow Implementing routing, serving static files, and handling user input with DTOs and Validation.     - W3: Security & Data Working with databases (ORMs), implementing Authentication (JWT), and utilizing advanced features like Pipes, Guards, and Interceptors.     - W4: Production Readiness Managing file uploads and configuring environment-specific settings. Before you jump in, make sure you're solid on the prerequisites: We have dedicated courses for these fundamental skills: - TypeScript: https://lnkd.in/g-P8FkKv     - Node.js: https://lnkd.in/gAfjKnWH     - SQL/Databases: https://lnkd.in/gqZynies    Dive into the full syllabus and materials here: https://lnkd.in/ghpGN7mb Let me know in the comments if you have any questions or what backend topic you're most excited to learn! 👇 #NestJS #BackendDevelopment #TypeScript #NodeJS #WebDevelopment #Programming #BaytAlHikmah #Workshops

I just shipped a major upgrade to react-snap-state and it changes everything Last week I released react-snap-state, a key-based state management library built on useSyncExternalStore. Since then, I have been refining the internals and rethinking the API design. Today’s update brings two major upgrades and one important architectural shift: 🚀 New in this release 1. useDeriveValue A lightweight way to compute derived state from one or more store keys with automatic subscriptions and comparator support. 2. Async setter Async state updates are now first-class. You can show a placeholder instantly, run your async work, and have the final value update the store automatically. 🧠 What I redesigned Comparators now live only on reads, not writes. This follows a simple philosophy: 𝐖𝐫𝐢𝐭𝐞𝐬 𝐬𝐡𝐨𝐮𝐥𝐝 𝐛𝐞 𝐝𝐮𝐦𝐛. 𝐑𝐞𝐚𝐝𝐬 𝐬𝐡𝐨𝐮𝐥𝐝 𝐛𝐞 𝐬𝐦𝐚𝐫𝐭. This makes behavior fully predictable and eliminates hidden complexity inside setters. Why this matters? react-snap-state now feels even closer to how React wants you to manage state: - isolated subscriptions - no context re-renders - concurrent-safe - minimal API If you're curious and want a tiny alternative to RTK/Zustand/Jotai for key-based state, check it out: 👉 npm: https://lnkd.in/dBwrGcmk 👉 GitHub: https://lnkd.in/dF7HqVTr Excited to keep improving this. Helps me learn a lot about react internals and state management. #ReactJS #JavaScript #TypeScript #OpenSource #WebDev