<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Openspec on It Might be Working</title><link>https://iguessthatworks.com/tags/openspec/</link><description>Recent content in Openspec on It Might be Working</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>Jeff Mayeur</copyright><lastBuildDate>Tue, 10 Nov 2026 07:00:00 -0700</lastBuildDate><atom:link href="https://iguessthatworks.com/tags/openspec/index.xml" rel="self" type="application/rss+xml"/><item><title>Lock-Driven Development</title><link>https://iguessthatworks.com/posts/11-2026/legos/</link><pubDate>Tue, 10 Nov 2026 07:00:00 -0700</pubDate><guid>https://iguessthatworks.com/posts/11-2026/legos/</guid><description>
&lt;p&gt;TL;DR - Be an engineer, map your flow before you go.&lt;/p&gt;
&lt;p&gt;I'm a fan of the &lt;a href="https://openspec.dev"&gt;OpenSpec&lt;/a&gt; flow. It's a linear approach with gates, both to read through what's been done and to implicitly validate the work. That's something I think belongs in any software factory.&lt;/p&gt;
&lt;p&gt;Recently I've been going through my list of old projects, some from a decade ago or more, and deciding if it's worth modernizing. Last week it was a photo frame that loops through all of the photos on my NAS that were taken on that day of the year. It used fbi (&amp;quot;framebuffer imageviewer&amp;quot;), which led to a lot of interesting Google searches when I first built that project in 2017.&lt;/p&gt;</description></item></channel></rss>