<h2>Conclusion: Professionalism</h2> <p>Clean code is not perfectionism—it’s respect for your future self and your teammates. Leave the codebase better than you found it. Refactor continuously, review each other’s work, and never accept “it works” as a substitute for “it’s clean.”</p>

<h2>Introduction</h2> <p>Clean code is not a luxury—it's a necessity. Code is read far more often than it is written. This guide distills the core ideas from Robert C. Martin’s <em>Clean Code</em> and decades of collective experience into actionable rules. You will learn how to name variables, write functions, handle errors, and structure classes so that your code tells a story, not a puzzle.</p>

<div class="bad"> <code>// increment i by 1<br />i++;</code> </div> <div class="good"> <code>// Retry up to 3 times due to eventual consistency in payment service<br />for (int attempt = 0; attempt < 3; attempt++) { ... }</code> </div>

<h2>4. Formatting: Vertical Density and Horizontal Flow</h2> <p>Code formatting is communication. Use consistent rules.</p>

<h3>Rule 2: Avoid disinformation</h3> <p>Don't use <code>accountList</code> unless it’s actually a <code>List</code>. Prefer <code>accounts</code> or <code>accountGroup</code>.</p>

<div class="good"> <pre>// Instead of using Gson directly everywhere: public interface JsonParser { <T> T fromJson(String json, Class<T> type); } // Implement with Gson, Jackson, or System.Text.Json later.</pre> </div>

<h3>Rule 3: Make meaningful distinctions</h3> <div class="bad"> <code>getUserInfo()</code> and <code>getUserData()</code> — what’s the difference? </div> <div class="good"> <code>getUserProfile()</code> vs <code>getUserCredentials()</code> </div>

<h2>10. Code Smells and Heuristics (Quick Reference)</h2>