<?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 Vinod Kumar N V on Medium]]></title>
        <description><![CDATA[Stories by Vinod Kumar N V on Medium]]></description>
        <link>https://medium.com/@vinodkumarnv?source=rss-52aa3c2d6fce------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*KH7fktcU_w56V6SGphSDGg.jpeg</url>
            <title>Stories by Vinod Kumar N V on Medium</title>
            <link>https://medium.com/@vinodkumarnv?source=rss-52aa3c2d6fce------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 18:33:05 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@vinodkumarnv/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[My Home Server Isn’t a Toy Anymore – It’s Becoming Infrastructure]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@vinodkumarnv/my-home-server-isnt-a-toy-anymore-it-s-becoming-infrastructure-813bbafa0668?source=rss-52aa3c2d6fce------2"><img src="https://cdn-images-1.medium.com/max/1024/1*RVs6FNF567cepGEe3pdXnQ@2x.jpeg" width="1024"></a></p><p class="medium-feed-snippet">A few months ago, my home server was just &#x201C;a box that runs stuff.&#x201D;</p><p class="medium-feed-link"><a href="https://medium.com/@vinodkumarnv/my-home-server-isnt-a-toy-anymore-it-s-becoming-infrastructure-813bbafa0668?source=rss-52aa3c2d6fce------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@vinodkumarnv/my-home-server-isnt-a-toy-anymore-it-s-becoming-infrastructure-813bbafa0668?source=rss-52aa3c2d6fce------2</link>
            <guid isPermaLink="false">https://medium.com/p/813bbafa0668</guid>
            <dc:creator><![CDATA[Vinod Kumar N V]]></dc:creator>
            <pubDate>Sun, 01 Feb 2026 03:03:44 GMT</pubDate>
            <atom:updated>2026-02-01T03:03:44.875Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[First, What Is a Homelab (Really)?]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@vinodkumarnv/first-what-is-a-homelab-really-e997a9538ed4?source=rss-52aa3c2d6fce------2"><img src="https://cdn-images-1.medium.com/max/1536/1*w-Tg8xCTZpFm4X4RqlJZBg@2x.jpeg" width="1536"></a></p><p class="medium-feed-snippet">If you Google homelab, you&#x2019;ll see intimidating racks, blinking LEDs, enterprise switches, and people casually saying things like:</p><p class="medium-feed-link"><a href="https://medium.com/@vinodkumarnv/first-what-is-a-homelab-really-e997a9538ed4?source=rss-52aa3c2d6fce------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@vinodkumarnv/first-what-is-a-homelab-really-e997a9538ed4?source=rss-52aa3c2d6fce------2</link>
            <guid isPermaLink="false">https://medium.com/p/e997a9538ed4</guid>
            <category><![CDATA[homelab]]></category>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[self-hosted]]></category>
            <category><![CDATA[home-server]]></category>
            <category><![CDATA[linux]]></category>
            <dc:creator><![CDATA[Vinod Kumar N V]]></dc:creator>
            <pubDate>Sun, 18 Jan 2026 22:59:13 GMT</pubDate>
            <atom:updated>2026-01-19T07:55:07.241Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Why I Love AWS EC2 Over Shared Hosting]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@vinodkumarnv/why-i-love-aws-ec2-over-shared-hosting-42945628d93d?source=rss-52aa3c2d6fce------2"><img src="https://cdn-images-1.medium.com/max/1024/1*PssSf0OQxdn3-uKeKa52Kw@2x.jpeg" width="1024"></a></p><p class="medium-feed-link"><a href="https://medium.com/@vinodkumarnv/why-i-love-aws-ec2-over-shared-hosting-42945628d93d?source=rss-52aa3c2d6fce------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@vinodkumarnv/why-i-love-aws-ec2-over-shared-hosting-42945628d93d?source=rss-52aa3c2d6fce------2</link>
            <guid isPermaLink="false">https://medium.com/p/42945628d93d</guid>
            <category><![CDATA[hosting]]></category>
            <category><![CDATA[web]]></category>
            <category><![CDATA[aws]]></category>
            <dc:creator><![CDATA[Vinod Kumar N V]]></dc:creator>
            <pubDate>Fri, 11 Oct 2024 18:58:55 GMT</pubDate>
            <atom:updated>2024-10-11T18:58:55.412Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[How to Set Up VSCode for Salesforce Development]]></title>
            <link>https://medium.com/@vinodkumarnv/how-to-set-up-vscode-for-salesforce-development-f085dc0c56be?source=rss-52aa3c2d6fce------2</link>
            <guid isPermaLink="false">https://medium.com/p/f085dc0c56be</guid>
            <category><![CDATA[vscode]]></category>
            <category><![CDATA[salesforce]]></category>
            <category><![CDATA[vscode-extension]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[developer-tools]]></category>
            <dc:creator><![CDATA[Vinod Kumar N V]]></dc:creator>
            <pubDate>Wed, 02 Oct 2024 16:14:02 GMT</pubDate>
            <atom:updated>2024-10-02T16:14:02.527Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*G_BfJPsQkGvQmYUIqI9RnQ.png" /></figure><p>As Salesforce development grows in popularity, having the right tools is essential to streamline your workflow. One of the most versatile and widely used tools for Salesforce development is Visual Studio Code (VSCode). It offers a flexible, open-source environment that can be customized for Salesforce-specific needs. In this guide, I’ll walk you through setting up VSCode for Salesforce development, covering everything from the installation to key extensions that can boost productivity.</p><h3><strong>1. Why Use VSCode for Salesforce Development?</strong></h3><p>VSCode is lightweight, fast, and highly extensible with a rich ecosystem of extensions. For Salesforce development, it offers:</p><ul><li><strong>Seamless integration</strong> with Salesforce DX (SF) CLI</li><li><strong>Code completion and IntelliSense</strong> for Apex, Visualforce, and Lightning Web Components</li><li><strong>Built-in Git support</strong> for version control</li><li><strong>Customizable environment</strong> to suit your personal workflow</li></ul><h3>2. Prerequisites</h3><p>Before diving into the setup, ensure you have:</p><ul><li>A Salesforce Developer Org or a Salesforce DX-enabled Org</li><li>Salesforce CLI installed on your machine. If not, you can download it <a href="https://developer.salesforce.com/tools/sfdxcli">here</a> or It can also be installed through a npm package considering Node.js LTS version is installed.</li><li>Some features in Salesforce Extensions for VS Code depend upon the Java Platform, Standard Edition Development Kit (JDK). You need to have either version <a href="https://www.oracle.com/java/technologies/downloads/#java11">11</a>, version <a href="https://www.oracle.com/java/technologies/downloads/#java17">17</a>, or version <a href="https://www.oracle.com/java/technologies/downloads/#java21">21</a> of the JDK installed.</li><li>Node.js LTS version is installed, which is necessary for some Lightning Web Component development. Download Node.js from <a href="https://nodejs.org/">here</a>.</li></ul><h3>3. Installing Visual Studio Code</h3><p>First, download and install VSCode from the official website: <a href="https://code.visualstudio.com/">VSCode Download</a>.</p><p>Once installed, open VSCode and make sure it’s updated to the latest version. You can do this by navigating to <strong>Help &gt; Check for Updates</strong>.</p><h3>4. Salesforce Extensions for VSCode</h3><p>To make VSCode Salesforce-friendly, you’ll need to install the Salesforce Extension Pack. This includes a set of tools specifically tailored for Salesforce development. Follow these steps:</p><ul><li>Open VSCode and go to the <strong>Extensions</strong> view by clicking on the Extensions icon in the Activity Bar on the side of the window or using Ctrl+Shift+X.</li><li>In the search bar, type <strong>Salesforce Extension Pack</strong> and install it.</li></ul><p>The Salesforce Extension Pack contains several useful tools:</p><ul><li>The Salesforce Extension Pack installs these extensions.</li><li><a href="https://marketplace.visualstudio.com/items?itemName=salesforce.salesforcedx-vscode-core"><strong>Salesforce CLI Integration</strong></a><strong> </strong>This extension (salesforcedx-vscode-core) interacts with Salesforce CLI to provide core functionality.</li><li><a href="https://marketplace.visualstudio.com/items?itemName=salesforce.salesforcedx-vscode-apex"><strong>Apex</strong></a> This extension (salesforcedx-vscode-apex) uses the Apex Language Server to provide features such as syntax highlighting and code completion.</li><li><a href="https://marketplace.visualstudio.com/items?itemName=salesforce.salesforcedx-vscode-apex-debugger"><strong>Apex Interactive Debugger</strong></a><strong> </strong>This extension (salesforcedx-vscode-apex-debugger) enables VS Code to use the real-time Apex Debugger with your scratch orgs or to use ISV Customer Debugger for your subscribers’ orgs.</li><li><a href="https://marketplace.visualstudio.com/items?itemName=salesforce.salesforcedx-vscode-apex-replay-debugger"><strong>Apex Replay Debugger</strong></a><strong> </strong>This extension (salesforcedx-vscode-apex-replay-debugger) enables VS Code to replay Apex execution from Apex debug logs.</li><li><a href="https://marketplace.visualstudio.com/items?itemName=salesforce.salesforcedx-vscode-lwc"><strong>Lightning Web Components</strong></a><strong> </strong>This extension supports Lightning web component bundles. It uses the HTML language server from VS Code.</li><li><a href="https://marketplace.visualstudio.com/items?itemName=salesforce.salesforcedx-vscode-lightning"><strong>Aura Components</strong></a> This extension (salesforcedx-vscode-lightning) supports Aura component bundles. It uses the HTML language server from VS Code.</li><li><a href="https://marketplace.visualstudio.com/items?itemName=salesforce.salesforcedx-vscode-visualforce"><strong>Visualforce</strong></a><strong> </strong>This extension (salesforcedx-vscode-visualforce) supports Visualforce pages and components. It uses the Visualforce Language Server and the HTML language server from VS Code.</li><li><a href="https://marketplace.visualstudio.com/items?itemName=salesforce.salesforcedx-vscode-soql"><strong>SOQL</strong></a><strong> </strong>This extension (salesforcedx-vscode-soql) enables you to interactively build a SOQL query via a form-based visual editor, view the query as you build, and save the output to a .csv or .json file.</li><li><a href="https://marketplace.visualstudio.com/items?itemName=salesforce.salesforce-vscode-slds"><strong>Salesforce Lightning Design System (SLDS) Validator</strong></a><strong> </strong>This extension (salesforcedx-vscode-slds) simplifies working with the Salesforce Lightning Design System (SLDS). It provides code completion, syntax highlighting, and validation with recommended tokens and utility classes.</li></ul><h3>5. Setting Up Salesforce DX (SF) CLI</h3><p>Once you have the Salesforce CLI installed, connect it with your Salesforce org using the following steps:</p><ul><li>Open the terminal in VSCode by navigating to <strong>View &gt; Terminal</strong> or pressing Ctrl+ (backtick).</li><li>Run the command:</li></ul><pre>sf org login web</pre><p>This command will open a web browser prompting you to log in to your Salesforce org.</p><p>Once logged in, your VSCode will be connected to your org. You can verify the connection by running:</p><pre>sf org open</pre><p>This command opens your Salesforce org in the browser.</p><p>6. <strong>Creating a New Project</strong></p><p>To create a new Salesforce project, use the Salesforce CLI command in VSCode’s terminal:</p><pre>sf project generate --name MyProject</pre><p>Replace MyProject with your project name. This command generates a folder structure, setting up the environment for Salesforce development.</p><h3>7. Working with Apex Code</h3><p>With the Salesforce Extension Pack installed, VSCode automatically enables features like:</p><ul><li><strong>Syntax highlighting</strong> for Apex and Visualforce.</li><li><strong>Code IntelliSense</strong> for Apex, making coding easier and faster.</li></ul><p>To create an Apex class or trigger, use the following steps:</p><ul><li>Open the command palette (Ctrl+Shift+P).</li><li>Type <strong>SFDX: Create Apex Class</strong> or <strong>SFDX: Create Apex Trigger</strong> and follow the prompts.</li></ul><h3>8. Setting Up Lightning Web Components (LWC)</h3><p>If you’re developing Lightning Web Components (LWC), you’ll need to ensure Node.js is installed. Once that’s set, you can create a new LWC:</p><ul><li>Open the command palette (Ctrl+Shift+P).</li><li>Type <strong>SFDX: Create Lightning Web Component</strong> and select the directory where the component should be created.</li></ul><p>This will generate the boilerplate code for your component. From here, you can start building your LWC by customizing the HTML, JavaScript, and CSS files.</p><h3>9. Using Git for Version Control</h3><p>VSCode has built-in Git support, which makes it easy to manage version control for your Salesforce projects. Here’s how to get started:</p><ul><li>Initialize a Git repository in your project folder by opening the terminal and typing:</li></ul><pre>git init</pre><p>To commit changes, go to the Source Control view in VSCode (or press Ctrl+Shift+G), stage your changes, and write a commit message.</p><p>You can also link your project to a remote repository like GitHub or Bitbucket for collaboration or backup.</p><h3>10. Bonus Tips</h3><ul><li><strong>Code Linting:</strong> Use ESLint for LWC to ensure consistent code quality. You can install the <strong>ESLint</strong> extension from the VSCode marketplace.</li><li><strong>Salesforce Code Analyzer</strong>: Scan your code against multiple rule engines to produce lists of violations and improve your code, to know more follow this link <a href="https://developer.salesforce.com/docs/platform/salesforce-code-analyzer/guide/code-analyzer-vs-code-extension.html">Salesforce Code Analyzer docs</a>.</li><li><strong>Prettier:</strong> Format your code automatically by installing the <strong>Prettier — Code formatter</strong> extension, do not forget to install npm package <a href="https://www.npmjs.com/package/prettier-plugin-apex">prettier-plugin-apex</a>.</li><li><strong>Snippets:</strong> Use Salesforce-specific code snippets for faster development.</li></ul><h3>Conclusion</h3><p>VSCode, when set up properly, can drastically improve your productivity as a Salesforce developer. The combination of the Salesforce Extension Pack, CLI integration, and the ability to customize your environment makes it the go-to tool for modern Salesforce development. Whether you’re working with Apex, Lightning Web Components, or managing your codebase with Git, VSCode provides all the tools you need to succeed.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f085dc0c56be" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>