<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Craftsmanship on Dadbot</title><link>https://dadbot.blog/categories/craftsmanship/</link><description>Recent content in Craftsmanship on Dadbot</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Sat, 03 Feb 2024 00:00:00 +0000</lastBuildDate><atom:link href="https://dadbot.blog/categories/craftsmanship/index.xml" rel="self" type="application/rss+xml"/><item><title>Book Review: Clean Code by Robert C. Martin</title><link>https://dadbot.blog/books/clean-code-review/</link><pubDate>Sat, 03 Feb 2024 00:00:00 +0000</pubDate><guid>https://dadbot.blog/books/clean-code-review/</guid><description>&lt;h2 id="the-short-version"&gt;The Short Version&lt;/h2&gt;
&lt;p&gt;Clean Code is still a strong guide for writing readable, maintainable code, but a few sections show their age.&lt;/p&gt;
&lt;h3 id="what-still-works"&gt;What Still Works&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Naming conventions that optimize for clarity&lt;/li&gt;
&lt;li&gt;Small, focused functions&lt;/li&gt;
&lt;li&gt;Consistent formatting and structure&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id="what-feels-dated"&gt;What Feels Dated&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Some Java-specific examples&lt;/li&gt;
&lt;li&gt;A few rules feel absolute when they should be situational&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id="how-i-use-it-now"&gt;How I Use It Now&lt;/h3&gt;
&lt;p&gt;I keep the principles, not the prescriptions. The big win is aligning a team around shared readability goals.&lt;/p&gt;</description><content:encoded><![CDATA[<h2 id="the-short-version">The Short Version</h2>
<p>Clean Code is still a strong guide for writing readable, maintainable code, but a few sections show their age.</p>
<h3 id="what-still-works">What Still Works</h3>
<ul>
<li>Naming conventions that optimize for clarity</li>
<li>Small, focused functions</li>
<li>Consistent formatting and structure</li>
</ul>
<h3 id="what-feels-dated">What Feels Dated</h3>
<ul>
<li>Some Java-specific examples</li>
<li>A few rules feel absolute when they should be situational</li>
</ul>
<h3 id="how-i-use-it-now">How I Use It Now</h3>
<p>I keep the principles, not the prescriptions. The big win is aligning a team around shared readability goals.</p>
<h3 id="rating-45">Rating: 4/5</h3>
<p>Great for teams and early-career developers. Skim the examples, focus on the principles.</p>
]]></content:encoded></item></channel></rss>