<?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"><channel><title><![CDATA[Esa Reynor]]></title><description><![CDATA[Esa Reynor]]></description><link>https://hashnode.rachmanesa.com</link><generator>RSS for Node</generator><lastBuildDate>Thu, 14 May 2026 07:59:28 GMT</lastBuildDate><atom:link href="https://hashnode.rachmanesa.com/rss.xml" rel="self" type="application/rss+xml"/><language><![CDATA[en]]></language><ttl>60</ttl><item><title><![CDATA[Why Every Developer Should Be a Lifelong Learner]]></title><description><![CDATA[A few months ago, I was overthinking some random news that showed me how AI helps developers write code better. It demonstrated how AI suggests code to developers while they are writing a function. I was amazed at how this could change everything. Th...]]></description><link>https://hashnode.rachmanesa.com/why-every-developer-should-be-a-lifelong-learner</link><guid isPermaLink="true">https://hashnode.rachmanesa.com/why-every-developer-should-be-a-lifelong-learner</guid><category><![CDATA[Developer]]></category><category><![CDATA[reflection]]></category><category><![CDATA[learning]]></category><dc:creator><![CDATA[Rachman Esa]]></dc:creator><pubDate>Tue, 26 Nov 2024 02:54:46 GMT</pubDate><content:encoded><![CDATA[<p>A few months ago, I was overthinking some random news that showed me how AI helps developers write code better. It demonstrated how AI suggests code to developers while they are writing a function. I was amazed at how this could change everything. Then I realized how this could become more challenging for us.</p>
<p>For me, this advancement means one thing: the bar is always being raised. Many companies will use AI with their codebase or code patterns. This helps developers, but at the same time, they might not fully understand what has been written because everything is AI-generated. This could be a worst-case scenario in the future. For example, when you need to transfer knowledge to your team, how can you explain the logic if you don't understand the code? AI can be a powerful ally in improving efficiency and catching errors, but it should complement your skills, not replace them.</p>
<h3 id="heading-the-necessity-of-learning">The Necessity of Learning</h3>
<p>Every developer is unique, and it depends on how much they learn each day. The more they learn, the more unique they become. Learning is the key to reaching your goals and demonstrating how well you solve problems. You can learn from your experiences, articles, journals, groups, and many other sources. By learning, you can combine two methods that have never been thought of before.</p>
<h3 id="heading-adapt-or-fade-away">Adapt or Fade Away</h3>
<p>The world of technology never stops changing. What is new today might be old tomorrow. If developers do not keep learning, they risk falling behind. Adapting to change is not just a choice. It is a necessity to stay relevant and grow in your career.</p>
<blockquote>
<p>“Change is not something to fear. It is a chance to grow stronger.”</p>
</blockquote>
<p>When you learn new skills, you prepare yourself for the future. Being flexible and open to change makes you a better problem solver and more valuable to any team. Remember, success belongs to those who embrace change, not run from it.</p>
<h3 id="heading-legacy-as-a-developer">Legacy as a Developer</h3>
<p>What do you want to leave behind as a developer? Your legacy is not just about the code you write but the impact you create. When you keep learning, you build tools, systems, and ideas that can inspire and help others for years to come.</p>
<blockquote>
<p>“A meaningful life is one that leaves the world better than you found it.”</p>
</blockquote>
<p>By staying curious and growing your skills, you teach others the value of constant improvement. Your dedication can spark a passion for learning in the next generation, ensuring that your work and wisdom live on through them.</p>
<h3 id="heading-finale">Finale</h3>
<p>Being a developer is not just about writing code; it's about growing, adapting, and making a positive impact on the world. The journey of learning never really ends, and that's what makes it beautiful. Every new skill, every mistake, and every success adds a chapter to your story, a story that will inspire others long after you're gone.</p>
<p>Take a moment to ask yourself: are you growing, or are you standing still? The choice is always yours. Choose growth. Choose curiosity. Choose to be a lifelong learner.</p>
]]></content:encoded></item><item><title><![CDATA[Preparing Your VPS Environment for NextJS Deployment]]></title><description><![CDATA[Deploying a Next.js application to a Virtual Private Server (VPS) can be an efficient way to host your web application while maintaining control over the server environment. Next.js, a popular React framework, offers server-side rendering and other p...]]></description><link>https://hashnode.rachmanesa.com/preparing-your-vps-environment-for-nextjs-deployment</link><guid isPermaLink="true">https://hashnode.rachmanesa.com/preparing-your-vps-environment-for-nextjs-deployment</guid><category><![CDATA[Next.js]]></category><category><![CDATA[vps]]></category><category><![CDATA[server]]></category><category><![CDATA[deployment]]></category><dc:creator><![CDATA[Rachman Esa]]></dc:creator><pubDate>Thu, 02 May 2024 01:30:59 GMT</pubDate><enclosure url="https://cdn.hashnode.com/res/hashnode/image/upload/v1714613405882/4b96a815-9ebc-43e9-8690-263c5d301aac.jpeg" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>Deploying a Next.js application to a Virtual Private Server (VPS) can be an efficient way to host your web application while maintaining control over the server environment. Next.js, a popular React framework, offers server-side rendering and other performance benefits, making it a preferred choice for building dynamic web applications. In this article, we'll walk through the steps to prepare your VPS environment for hosting a Next.js application.</p>
<h3 id="heading-step-1-choose-a-vps-provider">Step 1 : Choose a VPS Provider</h3>
<p>Select a reliable VPS provider that meets your requirements in terms of performance, scalability, and budget. Popular providers include DigitalOcean, AWS EC2, Linode, and Google Cloud Platform. Consider factors such as server location, pricing plans, and support services before making a decision.</p>
<h3 id="heading-step-2-provision-your-vps">Step 2 : Provision Your VPS</h3>
<p>Once you've chosen a VPS provider, provision a new virtual server instance. Choose an operating system that is compatible with Next.js, such as Ubuntu or CentOS. Configure the server specifications according to your application's requirements, including CPU, memory, and storage.</p>
<h3 id="heading-step-3-secure-your-server">Step 3 : Secure Your Server</h3>
<p>Before proceeding with any further setup, it's crucial to secure your server to prevent unauthorized access and potential security breaches. This includes setting up a firewall, disabling root login, and configuring SSH key-based authentication. Install and configure fail2ban to protect against brute-force attacks and regularly update the server's software packages to patch any security vulnerabilities.</p>
<h3 id="heading-step-4-install-nodejs-and-npm">Step 4 : Install NodeJS and npm</h3>
<p>Next.js applications require Node.js and npm (Node Package Manager) to run. Install the latest stable version of Node.js on your VPS using a package manager such as apt for Ubuntu or yum for CentOS. Additionally, verify the installation and ensure that npm is also installed correctly.</p>
<h3 id="heading-step-5-set-up-a-reverse-proxy-optional">Step 5 : Set Up a Reverse Proxy (Optional)</h3>
<p>To serve your Next.js application over the standard HTTP or HTTPS protocols, you can set up a reverse proxy server such as Nginx or Apache. Configure the reverse proxy to forward incoming requests to the appropriate port where your Next.js application is running. This step is optional but recommended for better performance and security.</p>
<h3 id="heading-step-6-clone-your-nextjs-repository">Step 6 : Clone your NextJS Repository</h3>
<p>Clone your Next.js application repository from your version control system (e.g., GitHub, Bitbucket) to your VPS. Ensure that all necessary dependencies are included in the repository and install them using npm install if needed.</p>
<h3 id="heading-step-7-configure-environment-variables">Step 7 : Configure Environment Variables</h3>
<p>Next.js applications often rely on environment variables for configuration, such as API keys, database connection strings, and server settings. Set up environment variables on your VPS to match those required by your Next.js application. You can use a .env file or specify them directly in your server's environment configuration.</p>
<h3 id="heading-step-8-build-and-start-your-nextjs-application">Step 8 : Build and Start your NextJS Application</h3>
<p>Before launching your Next.js application, build the project using npm run build. This command compiles your code and generates static assets ready for production deployment. Once the build process is complete, start your Next.js application using npm run start or any other custom start script specified in your package.json file.</p>
<h3 id="heading-step-9-monitor-and-mantain-your-server">Step 9 : Monitor and Mantain Your Server</h3>
<p>Regularly monitor your VPS environment to ensure optimal performance and reliability. Use monitoring tools such as Prometheus, Grafana, or New Relic to track server metrics, resource utilization, and application performance. Implement automated backups, security updates, and system maintenance routines to keep your server running smoothly.</p>
<h3 id="heading-conclusion">Conclusion</h3>
<p>By following these step-by-step instructions, you can effectively prepare your VPS environment for hosting a Next.js application. From provisioning your server to securing it and deploying your application, each step plays a crucial role in ensuring a stable and efficient hosting environment. With proper configuration and maintenance, you can confidently deploy and scale your Next.js applications on your VPS with ease.</p>
]]></content:encoded></item><item><title><![CDATA[A Guide to Mapping Custom Domains on Hashnode]]></title><description><![CDATA[Unlocking Your Website's Potential: A Guide to Mapping Custom Domains on Hashnode
So, you've built a fantastic blog or website on Hashnode and now you're ready to take it to the next level by mapping it to your custom domain. This step-by-step guide ...]]></description><link>https://hashnode.rachmanesa.com/a-guide-to-mapping-custom-domains-on-hashnode</link><guid isPermaLink="true">https://hashnode.rachmanesa.com/a-guide-to-mapping-custom-domains-on-hashnode</guid><category><![CDATA[Hashnode]]></category><dc:creator><![CDATA[Rachman Esa]]></dc:creator><pubDate>Thu, 28 Mar 2024 04:23:07 GMT</pubDate><enclosure url="https://cdn.hashnode.com/res/hashnode/image/upload/v1712021536205/e9c7f31d-4721-4620-b5dd-054b28eb7672.jpeg" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>Unlocking Your Website's Potential: A Guide to Mapping Custom Domains on Hashnode</p>
<p>So, you've built a fantastic blog or website on Hashnode and now you're ready to take it to the next level by mapping it to your custom domain. This step-by-step guide will walk you through the process, ensuring that your online presence reflects your unique brand identity.</p>
<h3 id="heading-why-map-to-a-custom-domain"><strong>Why Map to a Custom Domain?</strong></h3>
<p>Before we dive into the technical details, let's quickly touch on why mapping to a custom domain is essential. While Hashnode provides you with a default subdomain (e.g., yourblog.hashnode.dev), using a custom domain (e.g., <a target="_blank" href="http://www.yourblog.com/">www.yourblog.com</a>) offers several advantages:</p>
<ol>
<li><p><strong>Professionalism:</strong> A custom domain adds credibility to your website, making it appear more professional and trustworthy to your audience.</p>
</li>
<li><p><strong>Brand Identity:</strong> Your domain is an integral part of your brand identity. Using a custom domain allows you to reinforce your brand and make it more memorable.</p>
</li>
<li><p><strong>SEO Benefits:</strong> A custom domain can positively impact your search engine rankings, making it easier for people to find your website online.</p>
</li>
</ol>
<h3 id="heading-steps-to-map-your-custom-domain-on-hashnode"><strong>Steps to Map Your Custom Domain on Hashnode</strong></h3>
<p>Now, let's get into the nitty-gritty of mapping your custom domain on Hashnode. Follow these steps carefully, and you'll have your website up and running on your custom domain in no time:</p>
<ol>
<li><p><strong>Choose Your Domain Registrar:</strong> If you haven't already, register a domain name with a domain registrar of your choice. Popular options include GoDaddy, Namecheap, and Google Domains.</p>
</li>
<li><p><strong>Access Your Domain Settings:</strong> Log in to your domain registrar's website and navigate to the domain management or DNS settings section.</p>
</li>
<li><p><strong>Add DNS Records:</strong> In your domain settings, add the necessary DNS records to point your domain to Hashnode's servers. This typically involves creating an A record and/or a CNAME record pointing to Hashnode's IP addresses.</p>
</li>
<li><p><strong>Verify Ownership:</strong> Once you've added the DNS records, return to your Hashnode dashboard and navigate to the domain settings section. Enter your custom domain and follow the verification steps to confirm ownership.</p>
</li>
<li><p><strong>Enable SSL:</strong> Hashnode automatically provisions SSL certificates for custom domains, ensuring that your website is secure. Once the domain is verified, enable SSL in your Hashnode settings to encrypt the connection.</p>
</li>
<li><p><strong>Wait for DNS Propagation:</strong> DNS changes can take some time to propagate across the internet. Be patient, and give it some time for the changes to take effect. This process usually takes a few hours but can sometimes take up to 48 hours.</p>
</li>
<li><p><strong>Test Your Domain:</strong> Once DNS propagation is complete, test your custom domain to ensure that it's correctly mapped to your Hashnode blog or website. You should be able to access your website using your custom domain in a web browser.</p>
</li>
</ol>
<h3 id="heading-conclusion"><strong>Conclusion</strong></h3>
<p>Mapping your Hashnode blog or website to a custom domain is a straightforward process that can have a significant impact on your online presence. By following the steps outlined in this guide, you can enhance your brand, improve your website's credibility, and make it easier for your audience to find you online. So, what are you waiting for? Unlock the full potential of your website by mapping it to your custom domain today!</p>
]]></content:encoded></item></channel></rss>