<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Pycalphad on bocklund.io</title>
		<link>https://bocklund.io/tags/pycalphad/</link>
		<description>Recent content in Pycalphad on bocklund.io</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
			<copyright>Brandon Bocklund</copyright>
		
		
			<lastBuildDate>Sun, 30 Aug 2026 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://bocklund.io/tags/pycalphad/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Reviewing phase diagrams</title>
				<link>https://bocklund.io/reviewing-phase-diagrams/</link>
				<pubDate>Sun, 30 Aug 2026 00:00:00 +0000</pubDate>
				<guid>https://bocklund.io/reviewing-phase-diagrams/</guid>
				<description>&lt;p&gt;I want to start writing more about how I&#39;m using LLMs to create more leverage in my software development workflows.&#xA;LLM coding agents are getting really good, but I think they still require a lot of work to not create slop in brownfield projects (see &lt;a href=&#34;https://www.scbench.ai&#34;&gt;SlopCodeBench&lt;/a&gt;).&lt;/p&gt;&#xA;&lt;p&gt;My opinion is that if it&#39;s important to my job or someone else&#39;s job that the answer produced by a tool is correct, then a human needs to fully understand the system they are building and working in.&#xA;I don&#39;t think I&#39;m doing anything particularly novel, but I thought it might be nice to show what I&#39;m doing to create more leverage, go faster, and be more ambitious.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
