<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Essential Coding Principles on Abhyuday Pundir</title><link>https://abhyuday-fr.github.io/essential-coding-principles/</link><description>Recent content in Essential Coding Principles on Abhyuday Pundir</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 19 Aug 2026 09:25:09 +0530</lastBuildDate><atom:link href="https://abhyuday-fr.github.io/essential-coding-principles/index.xml" rel="self" type="application/rss+xml"/><item><title>DRY</title><link>https://abhyuday-fr.github.io/essential-coding-principles/dry/</link><pubDate>Wed, 19 Aug 2026 09:25:09 +0530</pubDate><guid>https://abhyuday-fr.github.io/essential-coding-principles/dry/</guid><description>&lt;p&gt;&amp;ldquo;Every piece of knowledge must have a single, unambiguous,&#10;authoritative representation within a system.&amp;rdquo; referenced by &lt;a href="https://pragprog.com/titles/tpp20/the-pragmatic-programmer-20th-anniversary-edition/"&gt;The Pragmatic Programmer&lt;/a&gt;.&lt;/p&gt;&#10;&lt;p&gt;DRY is more than code. Here’s the acid test: when some single facet of the code has to&#10;change, do you find yourself making that change in multiple&#10;places, and in multiple different formats? Do you have to&#10;change code and documentation, or a database schema and a&#10;structure that holds it, or…? If so, your code isn’t DRY.&lt;/p&gt;</description></item><item><title>ETC</title><link>https://abhyuday-fr.github.io/essential-coding-principles/etc/</link><pubDate>Fri, 07 Aug 2026 20:03:11 +0530</pubDate><guid>https://abhyuday-fr.github.io/essential-coding-principles/etc/</guid><description>&lt;p&gt;As quoted in the book of &lt;a href="https://pragprog.com/titles/tpp20/the-pragmatic-programmer-20th-anniversary-edition/"&gt;The Pragmatic Programmer&lt;/a&gt;, &amp;ldquo;Good design is easier to change than bad design&amp;rdquo;.&lt;/p&gt;&#10;&lt;p&gt;The book also mentions that ETC is a &lt;em&gt;value&lt;/em&gt; and &lt;strong&gt;NOT&lt;/strong&gt; a rule.&#10;Values are things that help you make decisions: should I do this,&#10;or that? When it comes to thinking about software, ETC is a&#10;guide, helping you choose between paths. Just like all your&#10;other values, it should be floating just behind your conscious&#10;thought, subtly nudging you in the right direction.&lt;/p&gt;</description></item></channel></rss>