<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Code on Lorbic</title><link>http://localhost:1313/tags/code/</link><description>Recent content in Code on Lorbic</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 06 Nov 2025 22:01:23 +0530</lastBuildDate><atom:link href="http://localhost:1313/tags/code/index.xml" rel="self" type="application/rss+xml"/><item><title>Understanding Private-Public Key Encryption</title><link>http://localhost:1313/private-public-key-encryption/</link><pubDate>Thu, 06 Nov 2025 22:01:23 +0530</pubDate><guid>http://localhost:1313/private-public-key-encryption/</guid><description>&lt;p>In today&amp;rsquo;s digital world, where secure communication, authentication, and data integrity are non-negotiable, &lt;strong>private-public key encryption&lt;/strong> (also called &lt;em>asymmetric cryptography&lt;/em>) plays a foundational role. From HTTPS in your browser to SSH logins, cryptocurrency wallets, and email encryption, this elegant cryptographic system enables trust without prior shared secrets.&lt;/p>
&lt;p>In this blog, we&amp;rsquo;ll dive into:&lt;/p>
&lt;ul>
&lt;li>The core concepts behind asymmetric encryption&lt;/li>
&lt;li>How it differs from symmetric encryption&lt;/li>
&lt;li>The mathematics (intuitively explained) behind popular algorithms like RSA and ECC&lt;/li>
&lt;li>Real-world examples and code snippets&lt;/li>
&lt;li>Common use cases and pitfalls&lt;/li>
&lt;/ul>
&lt;p>Whether you&amp;rsquo;re a curious beginner or a seasoned developer brushing up on fundamentals, you&amp;rsquo;ll find something valuable here.&lt;/p></description></item><item><title>The 5-Minute Refactor</title><link>http://localhost:1313/the-5-minute-refactor/</link><pubDate>Tue, 28 Oct 2025 02:01:23 +0530</pubDate><guid>http://localhost:1313/the-5-minute-refactor/</guid><description>&lt;h2 id="the-5-minute-refactoring-guide">The 5-Minute Refactoring Guide&lt;a class="anchorjs-link" href="#the-5-minute-refactoring-guide" aria-label="Link to section: The 5-Minute Refactoring Guide">&lt;/a>&lt;/h2>&lt;p>As experienced software engineers, we often face a dilemma: our codebases, like all physical systems, trend toward entropy. The gap between &amp;ldquo;getting it done&amp;rdquo; and &amp;ldquo;getting it right&amp;rdquo; grows, leading to sluggish feature delivery and inevitable technical debt. The solution isn&amp;rsquo;t a massive, heroic rewrite; it&amp;rsquo;s the disciplined, humble practice of &lt;strong>Kaizen&lt;/strong>, or continuous improvement.&lt;/p>
&lt;p>For Golang engineers, this translates to the &lt;strong>5-Minute Refactor&lt;/strong>: a daily commitment to making &lt;strong>one tiny, tangible, quality improvement&lt;/strong> to any code you touch. This practice leverages Go&amp;rsquo;s philosophy of simplicity to prevent decay and sharpen your engineering judgment, all in less time than it takes to make coffee.&lt;/p></description></item></channel></rss>