<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Piyush Yadav on Medium]]></title>
        <description><![CDATA[Stories by Piyush Yadav on Medium]]></description>
        <link>https://medium.com/@piyush9?source=rss-240c0da65be7------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*aFH_knQ0Dqpud2Wbt36Nlw.jpeg</url>
            <title>Stories by Piyush Yadav on Medium</title>
            <link>https://medium.com/@piyush9?source=rss-240c0da65be7------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 11:10:53 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@piyush9/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Why Most React Developers Eventually Learn Next.js]]></title>
            <link>https://medium.com/@piyush9/why-most-react-developers-eventually-learn-next-js-02820cd0e390?source=rss-240c0da65be7------2</link>
            <guid isPermaLink="false">https://medium.com/p/02820cd0e390</guid>
            <category><![CDATA[reactjs]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[nextjs]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Piyush Yadav]]></dc:creator>
            <pubDate>Mon, 15 Jun 2026 07:09:19 GMT</pubDate>
            <atom:updated>2026-06-15T07:09:19.769Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nwXlnj8h4oxf_ZfN4qTTYw.png" /></figure><p><strong>Next.js</strong> transforms React from a <strong>client-side user interface library</strong> into a <strong>full-stack framework</strong>.</p><p>Remember that <strong>React is a UI library</strong>, whereas <strong>Next.js is a framework</strong> built on top of React.</p><p>Why do many React developers end up learning Next.js?</p><ul><li>Because big companies like <strong>Netflix, Walmart, and Nike use Next.js</strong>.</li><li><strong>Job postings </strong>often list Next.js as a required skill for React developers.</li><li><strong>The official React team</strong> actively promotes Next.js for production-grade apps.</li></ul><p>So, let’s compare these two and know <strong>why official React team formally recommend</strong> starting with a <strong>full-stack React framework (like Next.js or Remix)</strong> for most production apps.</p><h3>1. What React Gives You</h3><p><strong>React was popular because</strong> it made building user interface way easier than before.</p><p>React provides some strong things at its core like <strong>Components</strong>, <strong>State Management</strong>,<strong> Hooks </strong>and<strong> Virtual DOM.</strong></p><p>But React mainly focuses on the UI layer.</p><p>There are <strong>no built-in solutions</strong> for things like:</p><ul><li>Routing</li><li><strong>SEO</strong></li><li>Server-Side Rendering (<strong>SSR</strong>)</li><li>Static Site Generation (<strong>SSG</strong>)</li><li>Image Optimization</li><li>API Routes</li></ul><p>You will <strong>generally need additional libraries</strong> or <strong>tools for these features</strong>.<br>That’s where <strong>Next.js</strong> comes into play.</p><h3>2. What Next.js adds on top of React</h3><p>React is great for building user interfaces. But as your app scales, you’ll likely need extra tools for <strong>routing, SEO, performance, and backend functionality.</strong></p><p>Next.js brings many of these features together in one framework.</p><h4>File-Based Routing</h4><ul><li>With React, you would typically use libraries such as <strong>react-router-dom </strong>to configure routes.</li><li><strong>Creating a file</strong> in Next.js <strong>creates a route</strong> and makes navigation much easier to set up.</li></ul><h4>Server-Side Rendering (SSR)</h4><ul><li>Next.js can <strong>render pages on the server</strong> before sending them to the browser.</li><li>This helps search engines understand your content and <strong>improves SEO</strong>.</li></ul><h4>Static Site Generation (SSG)</h4><ul><li>Pages can be generated during <strong>build time</strong> and <strong>served as static HTML.</strong></li><li>This makes the websites very fast and efficient.</li></ul><h4>Server Components</h4><ul><li>By <strong>default</strong>, Next.js uses <strong>Server Components.</strong></li><li>This means less JavaScript is sent to the browser, which can improve performance.</li></ul><h4>API Routes</h4><ul><li>With Next.js you can build <strong>backend API endpoints </strong>in the same project.</li><li><strong>For smaller applications</strong> you may not even need a backend server separately.</li></ul><h4>Image Optimization</h4><ul><li>The <strong>next/image</strong> component provides <strong>automatic image optimization</strong> for different devices and screen sizes.</li><li>This improves loading speed without extra effort.</li></ul><h4>Metadata API</h4><ul><li>Adding page titles, descriptions and other SEO related metadata is <strong>much easier in Next.js.</strong></li></ul><h4>Middleware</h4><ul><li>Middleware lets you run code before a request reaches a page.</li><li>It is often used for <strong>authentication</strong>, <strong>redirects</strong>, and <strong>route protection</strong>.</li></ul><h4>Automatic Optimizations</h4><ul><li><strong>Manual code splitting and asset configurations</strong> are complex in vanilla React.</li><li><strong>Next.js automates code-splitting</strong> to serve only the necessary JavaScript.</li></ul><p>All these features together make it easy to see <strong>why many developers choose Next.js</strong> for production applications instead of React alone.</p><h3>3. When React Is Enough</h3><p>Next.js has a lot of features, but in some situations <strong>React is still a great choice</strong>.</p><p><strong>If you’re learning frontend development</strong>, React helps you understand the fundamentals.</p><p>React is also a good option for:</p><ul><li>Internal company dashboards</li><li>Admin dashboards</li><li>Simple Single Page Applications (<strong>SPAs</strong>)</li><li>Projects where <strong>SEO doesn’t matter</strong></li></ul><p>In these cases, React can be <strong>simpler</strong> and <strong>give you more control</strong> over your setup.</p><h3>4. When Next.js Is Better</h3><p><strong>Next.js is better</strong> when performance, SEO, and scalability become important.</p><p>It has features such as SSR, SSG, Server Components, and built-in routing that can <strong>save a lot of development time.</strong></p><p>Next.js is often a better choice for:</p><ul><li>Blogs</li><li>Portfolio websites</li><li>SaaS products</li><li>E-commerce applications</li><li>SEO-focused websites</li></ul><p><strong>If your application needs</strong> to rank on <strong>search engines</strong>, <strong>load quickly</strong>, or serve content efficiently, Next.js will usually be the better option.</p><h3>5. Which One Should You Learn First?</h3><p>If you’re just <strong>starting</strong> your frontend journey, <strong>learn React first.</strong></p><p>You will learn about <strong>components, state management, hooks and working with APIs</strong> and will have a strong foundation to apply to any React framework.</p><p>Once you’re comfortable with React, learning Next.js becomes much easier because you’re simply building on concepts you already know.</p><h3>Conclusion</h3><p>React and Next.js <strong>aren’t competitors.</strong></p><p>React gives you the tools to build <strong>user interfaces</strong>, while <strong>Next.js adds features</strong> that help you build faster, more scalable, and SEO-friendly applications.</p><p><strong>If you’re building</strong> a simple dashboard or learning frontend development, React is often enough.</p><p><strong>But if you’re building production applications</strong> where performance, SEO, and developer experience matter, Next.js can save you a lot of time and effort.</p><p>At the end of the day,<strong> learning React first and then moving to Next.js</strong> is the path most developers follow.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=02820cd0e390" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Authentication Concepts Every Developer Should Know - Session, Token, JWT and OAuth2…]]></title>
            <link>https://medium.com/@piyush9/the-authentication-concepts-every-developer-should-know-session-token-jwt-and-oauth2-114e11a9bb10?source=rss-240c0da65be7------2</link>
            <guid isPermaLink="false">https://medium.com/p/114e11a9bb10</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Piyush Yadav]]></dc:creator>
            <pubDate>Thu, 04 Jun 2026 10:32:54 GMT</pubDate>
            <atom:updated>2026-06-04T10:45:10.050Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*moO0KOsVT3vDgGLVRyBPdg.png" /></figure><p>Authentication is the process of <strong>verifying a user’s identity. </strong>Before allowing a user to perform certain actions in an application, we first confirm who they are.</p><p>If the user is successfully authenticated, the application <strong>grants access</strong> to the requested resources or actions. If the user is not authenticated, the application typically returns a <strong>401 Unauthorized</strong> HTTP status code.</p><p>Now, lets talk about the type of authentication we can implement in our application.</p><h3>1. Session-based authentication</h3><p>When a user logs in, the <strong>server first verifies</strong> the username and password. If they’re correct, the server creates a session and stores information about that user. The session gets a <strong>unique ID, </strong>something like <strong>abc123xyz</strong>.</p><p>The server then sends this <strong>session ID</strong> to the browser inside a <strong>cookie</strong>.</p><p>Now, whenever the <strong>browser sends a request</strong>, that cookie is automatically included. The server reads the session ID, finds the matching session, and knows which user is making the request.</p><p><strong><em>The upside:</em></strong> It’s simple to implement. Logging someone out is easy; you just delete the session on the server. Done. That user’s cookie is now useless.</p><p><strong><em>The downside:</em></strong> The server must store session data, and Scaling becomes harder when multiple servers are involved.</p><h4>Common Use Cases</h4><ul><li>Banking applications</li><li>E-commerce websites</li></ul><h4>Simple Workflow-</h4><ol><li>User logs in with credentials.</li><li>Server verifies credentials and saves a new session in its storage.</li><li>Server sends the session ID to the browser inside a cookie.</li><li>Browser sends the cookie with every request.</li><li>Server matches the session ID against its storage to identify the user.</li></ol><h3>2. JWT (Token-Based) Authentication</h3><p>When a user logs in, the <strong>server verifies </strong>the username and password. If they’re correct, the server creates a <strong>JWT (JSON Web Token).</strong> This token contains information about the user, such as their ID or role, and is digitally signed using a <strong>secret key</strong>.</p><p>The <strong>server then sends this token to the client</strong>.</p><p>Now, whenever the client sends a request, it includes the JWT in the <strong>Authorization header.</strong> The server verifies the token’s signature and extracts the user information. If the signature is valid, the server knows who the user is without needing to look up session data.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*kxMnWvmV96JaWXeVWK8xyQ.jpeg" /><figcaption><strong>Structure of a JWT</strong></figcaption></figure><p><strong><em>The upside:</em> </strong>The server doesn’t need to store session information. It scales well and works great for APIs, mobile applications, and microservices.</p><p><strong><em>The downside:</em></strong> Invalidating a token before it expires can be difficult. Even after a user logs out, the token may remain valid until its expiration time. Solutions like token blacklists exist, but they add complexity.</p><h4>Common Use Cases</h4><ul><li>React and Next.js applications</li><li>Mobile applications</li><li><strong>Microservices architectures</strong>(any project where the frontend and backend are separate)</li></ul><h4>Simple Workflow-</h4><ol><li>User logs in with credentials.</li><li>Server verifies credentials and generates a JWT.</li><li>Then JWT is sent to the client, and the client stores the token.</li><li>Client sends the token with every request.</li><li>Server verifies the token and identifies the user.</li></ol><h3>3. OAuth Authentication (OAuth + OIDC)</h3><p>You’ve probably clicked a button like:</p><ul><li>Continue with Google</li><li>Continue with GitHub</li></ul><p>That’s what most developers refer to as <strong>OAuth login.</strong></p><p>When a user clicks “Continue with Google” or “Continue with GitHub”, the <strong>application redirects them</strong> to the provider. The user logs in there and gives permission <strong>to share basic profile information.</strong></p><p><strong>The provider then sends information about the user back to the application.</strong> The application can now <strong>create an account</strong> or <strong>log</strong> the user in without ever <strong>seeing their password.</strong></p><p>The important part is that your application never sees your <strong>Google password</strong>. Google handles the verification and simply tells your app who you are.</p><p><strong><em>The upside:</em></strong> Users can sign up in seconds without creating another password. Developers also don’t have to build features like password resets, email verification, and account recovery from scratch.</p><p><strong><em>The downside:</em></strong> Your login system now depends on a third-party provider. If the provider has issues or the integration breaks, users may not be able to sign in.</p><h4>OAuth2 vs OIDC</h4><p>OAuth2 is an <strong>authorization framework</strong>, not an authentication protocol. It answers what this app can access on behalf of the user.</p><p>OpenID Connect (OIDC) <strong>adds authentication on top of OAuth2.</strong> Most <strong>modern social logins </strong>use OpenID Connect (OIDC) on top of OAuth2.</p><p>After the user signs in, <strong>the provider returns an ID token (a JWT)</strong>. The application reads this token to know exactly who the user is.</p><p>So in simple terms:</p><ul><li><strong>OAuth2 </strong>handles<strong> authorization</strong></li><li><strong>OIDC </strong>handles<strong> authentication</strong></li></ul><h4>Common Use Cases</h4><ul><li>SaaS applications</li><li>Applications offering “Continue with Google” or “Continue with GitHub”</li></ul><h3>4. Multi-Factor Authentication (MFA)</h3><p>Unlike the other methods we’ve discussed, MFA isn’t a standalone authentication method. Instead, it’s an <strong>additional security layer</strong> added on top of an existing authentication system.</p><p><strong>For example</strong>, after entering a password, a user may be asked to enter a <strong>one-time code</strong> from an authenticator app or verify their identity using a <strong>fingerprint.</strong></p><p><strong><em>The upside:</em></strong> MFA significantly improves account security and helps protect against stolen or leaked passwords.</p><p><strong><em>The downside:</em></strong> It adds an extra step during login, which can make the sign-in process slightly less convenient for users.</p><h4>Common Use Cases</h4><ul><li>Banking applications</li><li>Applications handling sensitive user data</li></ul><h3>5. API Key Authentication</h3><p>This one is a bit different from the others. <strong>API keys don’t usually identify a <em>user, </em>they identify an <em>application</em>.</strong></p><p>When you sign up for the <strong>OpenAI API</strong>, you get a key like sk-abc123.... You put that <strong>key in your server-side code</strong>, and every request you make to OpenAI includes it. OpenAI uses the key to know which account is making the request, track usage, and enforce rate limits.</p><p><strong>Notice</strong> who’s involved here: it’s your <strong><em>application</em></strong>, <strong>not the person</strong> using your application.</p><p><strong><em>The limitation:</em></strong> API keys are meant to stay secret, on the server. You should never put them in your frontend JavaScript, and anyone can see them in the browser.</p><h4>Common Use Cases</h4><ul><li>Third-party APIs</li><li>AI services</li><li>Payment gateways</li></ul><h3>6. Magic Link Authentication</h3><p>What if you <strong>removed passwords entirely?</strong></p><p>Magic link authentication does exactly that. The user types their <strong>email</strong> address. The app sends them an email with a <strong>special login link,</strong> something like yourapp.com/auth?token=xyz789. The user <strong>clicks</strong> the link. The token is verified. <strong>They&#39;re logged in.</strong></p><p>The email itself becomes the proof of identity. If you <strong>can access</strong> this email inbox, you must be the person who owns this account.</p><p><strong>Where you’ll see it:</strong> Notion, Slack (as an option), a lot of developer.</p><h3>Conclusion -</h3><p>Authentication might seem complicated at first because of terms like <strong>Sessions</strong>, <strong>JWTs</strong>, <strong>OAuth</strong>, <strong>OIDC</strong>, and <strong>MFA</strong>. But all of these approaches are trying to solve the same problem:</p><p><strong>“How does the application know who you are?”</strong></p><p>The main difference is where the identity information is stored and how it’s verified.</p><ul><li><strong>Session Authentication</strong> → The server remembers you</li><li><strong>JWT Authentication</strong> → The client carries proof</li><li><strong>OAuth/OIDC </strong>→ Another provider verifies you</li><li><strong>API Keys</strong> → The application identifies itself</li><li><strong>MFA</strong> → Adds an extra layer of security</li><li><strong>Magic Link Auth</strong> → Passwordless authentication by sending a link</li></ul><p>Once you understand these core ideas, authentication becomes much easier to reason about, whether you’re building a simple web app or a large-scale production system.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=114e11a9bb10" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Simplest Explanation of Rendering Techniques like CSR, SSR, SSG, ISR, and RSC]]></title>
            <link>https://medium.com/@piyush9/the-simplest-explanation-of-rendering-techniques-like-csr-ssr-ssg-isr-and-rsc-fb28aa7cf3db?source=rss-240c0da65be7------2</link>
            <guid isPermaLink="false">https://medium.com/p/fb28aa7cf3db</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[nextjs]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Piyush Yadav]]></dc:creator>
            <pubDate>Sat, 09 May 2026 10:31:54 GMT</pubDate>
            <atom:updated>2026-06-04T10:46:23.699Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uKxxKnrSyo-uuTbyZvcxLA.png" /></figure><p>Most people fumble when explaining these concepts in interviews, or they’re completely clueless while explaining these concepts by giving textual definitions only.</p><p>But honestly, these concepts are much simpler when you stop looking at them as complicated rendering strategies and instead ask one question:</p><blockquote><em>“Where is the HTML being generated?”</em></blockquote><p>That’s literally the <strong>core idea</strong> behind almost all modern rendering patterns.</p><p><em>Once you understand this, frameworks like </em><strong><em>Next.js</em></strong><em> start making much more sense.</em></p><p>Let’s start.</p><h3>1. CSR - Client Side Rendering</h3><p>This is the default behavior of normal React apps.</p><p>Here’s what happens:</p><ul><li>The server sends a mostly empty <strong><em>HTML file</em> and <em>JS files</em></strong></li><li>The browser <strong>downloads the JS files</strong></li><li>React runs in the browser and <em>generates/updates the DOM</em></li><li>The browser renders the <em>final UI on the screen.</em></li></ul><p>So the rendering happens on the <strong>client side (browser)</strong>.<br>That’s why React apps sometimes show a blank white screen for a moment before loading.</p><h4>Why people still use CSR -</h4><p>Once the app loads, everything feels extremely <strong>smooth and fast</strong> because navigation happens without reloading the page.</p><p><em>That’s why dashboards, chat apps, and highly interactive apps often use CSR heavily.</em></p><h4><strong><em>The </em></strong>tradeoff<strong><em> -</em></strong></h4><p><strong>SEO.<br></strong>Search engines prefer ready HTML content. In CSR, the HTML is mostly empty initially, so SEO becomes weaker compared to server-rendered approaches as <em>the crawlers aren’t able to see the content in the HTML initially</em></p><h3>2. SSR - Server Side Rendering</h3><p>SSR flips the process.</p><p>Instead of the browser generating the page, the <strong>server generates the HTML first</strong> and sends a fully rendered page to the browser.</p><p>This means users can see content immediately.</p><h4>SSR is great when -</h4><ul><li>Data changes frequently</li><li><strong>SEO</strong> matters</li><li>You want fresh content on every request</li></ul><p><strong>Examples:</strong> E-commerce products, Social platforms</p><h4>The tradeoff -</h4><p>Since the server renders the page for every request, it can be slower and more expensive than serving static pages.</p><h3>3. SSG - Static Site Generation</h3><p>SSG is basically <strong>“pre-building”</strong> pages.</p><p>Instead of generating HTML on every request, the HTML is generated during <strong>build time and stored as static files.<br></strong>When users visit the page, the server simply sends that ready-made HTML instantly.</p><p>This makes <strong>SSG incredibly fast.</strong></p><h4>Best use cases</h4><p>SSG works best for pages that don’t change often:</p><ul><li>About pages</li><li>Blog posts</li><li>Landing pages</li></ul><p><em>This is one reason why Next.js became so popular.<br>It made static generation extremely easy.</em></p><h4>One important misconception</h4><p>People often think SSG means “the data is always old.”<br>Not necessarily.<br>Modern frameworks support <strong>revalidation and regeneration, which leads to ISR.</strong></p><h3>4. ISR - Incremental Static Regeneration</h3><p>ISR is like a mix of <strong>SSG</strong> and <strong>SSR</strong>.</p><p>The page is initially generated statically, but it can automatically regenerate in the background after a <strong>certain time interval.</strong></p><p>So you get:</p><ul><li>Static-site speed</li><li>Better scalability</li><li>Fresher data</li></ul><p><strong>Without rebuilding the entire application.</strong></p><p>This is extremely useful for :- blogs pages, product pages, <strong>large content websites</strong></p><p>Because rebuilding thousands of pages every time would be painful.</p><h3>5. RSC - React Server Components</h3><p>This is where many developers get confused.</p><p>React Server Components are <strong>not exactly another rendering strategy</strong> <strong>like CSR or SSR.</strong></p><p>Instead, they decide:</p><blockquote><strong>“Where should this component run?”</strong></blockquote><p>In modern Next.js apps:</p><ul><li><strong>Server Components</strong> run on the <strong>server</strong></li><li><strong>Client Components</strong> run in the <strong>browser</strong></li></ul><p>By <strong>default, components are server components.</strong></p><p>If you add:</p><pre>&quot;use client&quot;<br>// below component which will run on the client side</pre><p>then that component runs in the browser and can use:</p><ul><li>react hooks like useState &amp; useEffect</li><li>browser APIs</li></ul><h4>The biggest misunderstanding</h4><p>Many beginners think:<br><strong><em>&quot;use client&quot; = CSR</em></strong></p><p><strong>But that’s not true.<br><em>A page can still be server-rendered while containing client components inside it.</em></strong></p><h4>IN SUMMARY -</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*52-vHZI3lgUkBWCfu_c0lA.png" /></figure><p>Thank you for reading…</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fb28aa7cf3db" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Top 9 Vs code Extensions I use as a Full Stack web developer]]></title>
            <link>https://medium.com/@piyush9/top-9-vs-code-extensions-i-use-as-a-full-stack-web-developer-06b05dd68b01?source=rss-240c0da65be7------2</link>
            <guid isPermaLink="false">https://medium.com/p/06b05dd68b01</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[vscode]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Piyush Yadav]]></dc:creator>
            <pubDate>Mon, 12 Jan 2026 11:32:20 GMT</pubDate>
            <atom:updated>2026-01-12T11:32:20.455Z</atom:updated>
            <content:encoded><![CDATA[<p>I use VS Code every day while building my personal web projects. And extensions help me write code faster and with less stress.<br>These are the <strong>9 extensions(with their publishers name) I personally use and find very helpful</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*00fq1PsFgY7jfIGuyf_EYQ.png" /></figure><h3>1. Git Graph (mhutchie)</h3><p>I use Git Graph to understand my Git history. It shows branches and commits in a visual way, which is easier than the terminal.<br>Also it lets you undo all the changes just like it was in previous commit.</p><h3>2. Postman (Postman)</h3><p>I use Postman to test APIs while working on backend projects. It helps me check requests and responses quickly.<br><strong>Why using in vs code?</strong> To test a simple api if i am in hurry and wants to quickly check the response..</p><h3>3. Live Server (Ritwick Dey)</h3><p>Live Server helps me see changes instantly in the browser. I don’t need to refresh the page again and again.<br>(Works only for <strong>front-end web development</strong> with HTML, CSS, and JavaScript projects.)</p><h3>4. Prettier - Code Formatter</h3><p>Prettier formats my code automatically. My code looks clean and easy to read without extra effort.</p><h3>5. Tailwind CSS IntelliSense</h3><p>When I use Tailwind CSS, this extension gives class suggestions. It saves time and avoids mistakes.<br>You don’t have to remember all the classes just type few characters and then it will suggest all the classes related to it.</p><h3>6. Material Icon Theme (Philipp Kief)</h3><p>This extension adds icons to files and folders. It makes my project structure easy to understand. It gives a nice touch to plain vs code and you should definitely install this one.</p><h3>7. CodeSnap (adpyke)</h3><p>I use CodeSnap to take clean screenshots of code. It is useful for sharing code on social media or blogs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/726/1*4LJn59qyhdQlQhitpwjStQ.png" /></figure><h3>8. GitHub Copilot Chat</h3><p>Copilot Chat helps me understand code and get quick help while coding. It is useful when I am stuck at something and can’t understand it<br>Why its better? Because it has the context of the code and you can also send any file from the codebase to it.</p><h3>9. ES7+ React/Redux Snippets (dsznajder)</h3><p>This extension gives ready-made snippets for React. It helps me create components faster. You just need to create a file with extension of .jsx or .tsx and then write “rafce” and then you will see the option of creating a conponent.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/864/1*MRDhb9h9ZE8hHnLBmG1u7w.png" /></figure><h3>Final Thoughts</h3><p>These extensions make my daily coding work easier. I don’t use all features, but even basic usage improves productivity. If you are a web developer, these tools are worth trying.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=06b05dd68b01" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>