<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Posts on Bliggity Blog</title>
		<link>https://bliggityblog.com/posts/</link>
		<description>Recent content in Posts on Bliggity Blog</description>
		<generator>Hugo -- gohugo.io</generator>
		<language>en-us</language>
		<copyright>Yes</copyright>
		<lastBuildDate>Thu, 09 Jul 2026 03:37:36 -0400</lastBuildDate>
		<atom:link href="https://bliggityblog.com/posts/index.xml" rel="self" type="application/rss+xml" />
		
		<item>
			<title>Design Is Hard, for Now</title>
			<link>https://bliggityblog.com/posts/design-is-hard-for-now/</link>
			<pubDate>Thu, 09 Jul 2026 03:37:36 -0400</pubDate>
			
			<guid>https://bliggityblog.com/posts/design-is-hard-for-now/</guid>
			<description><![CDATA[%!s(<nil>)]]></description>
			<content type="html"><![CDATA[<p>LLMs are incredible at generating code.</p>
<p>They often consider corner cases that I wouldn&rsquo;t.</p>
<p>But without a scaffolding to keep them in check, one aspect is implemented completely differently from another.</p>
<p>Sort of like if you took multiple senior devs, and told them they could do whatever they wanted as long as the functionality worked.</p>
<p>LLMs are also incredible at following obvious conventions.</p>
<p>I&rsquo;ve been using LLMs to generate code for about a half year now.</p>
<p><img src="../github.png" alt="alt text"></p>
<p>It&rsquo;s really important to enforce a structure. This structure is currently enforced by me.</p>
<p>I haven&rsquo;t found that LLMs are good at creating &ldquo;good&rdquo; structure without specific direction.</p>
<p>So what you&rsquo;re really doing is iterating on design.</p>
]]></content>
		</item>
		
	</channel>
</rss>
