<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>
<ul> <li><strong>Rigidity</strong>: A small change breaks many parts → increase cohesion, reduce coupling.</li> <li><strong>Fragility</strong>: Changes cause unexpected failures → add tests, encapsulation.</li> <li><strong>Opacity</strong>: Code is hard to understand → rename, refactor, add explanatory variables.</li> <li><strong>Feature envy</strong>: A method seems more interested in another class’s data → move the method.</li> <li><strong>Long parameter list</strong>: Wrap parameters into an object (DTO).</li> </ul> codigo limpo epub
<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> // increment i by 1<
<hr />