<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Craft on Mo Jahani</title>
		<link>https://www.onlymaj.com/tags/craft/</link>
		<description>Recent content in Craft on Mo Jahani</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Tue, 09 Dec 2025 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://www.onlymaj.com/tags/craft/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Clean code is a feature, not a luxury</title>
				<link>https://www.onlymaj.com/blog/clean-code-is-a-feature/</link>
				<pubDate>Tue, 09 Dec 2025 00:00:00 +0000</pubDate>
				<guid>https://www.onlymaj.com/blog/clean-code-is-a-feature/</guid>
				<description>&lt;p&gt;&amp;ldquo;We&amp;rsquo;ll clean it up later&amp;rdquo; is the most expensive sentence in software, and it&amp;rsquo;s&#xA;expensive in a way that never shows up on the ticket that caused it.&lt;/p&gt;&#xA;&lt;p&gt;I&amp;rsquo;ve stopped arguing for clean code on aesthetic grounds. Nobody wins that&#xA;argument, and honestly nobody should: a beautiful codebase that ships nothing&#xA;is worth less than an ugly one that pays salaries. The argument that works is&#xA;narrower and harder to dismiss: &lt;strong&gt;readable code is faster to repair under&#xA;pressure&lt;/strong&gt;, and every system eventually needs repairing under pressure.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
