<?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>Development on Josh Wise</title>
    <link>https://jwise.dev/tags/development/</link>
    <description>Recent content in Development on Josh Wise</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 06 Nov 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://jwise.dev/tags/development/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Faster Than I Should</title>
      <link>https://jwise.dev/posts/faster-than-i-should/</link>
      <pubDate>Fri, 06 Nov 2026 00:00:00 +0000</pubDate>
      <guid>https://jwise.dev/posts/faster-than-i-should/</guid>
      <description>&lt;p&gt;Last year I read raf&amp;rsquo;s post, &lt;a href=&#34;https://notashelf.dev/posts/curse-of-knowing&#34;&gt;The Curse of Knowing&lt;/a&gt;, and it described a feeling I&amp;rsquo;ve had for most of my career. Once you understand how software works, you stop being able to ignore it when it doesn&amp;rsquo;t. Every clunky workflow and half-working tool starts to look like something you should fix.&lt;/p&gt;
&lt;p&gt;raf lands on a line I keep coming back to:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&amp;ldquo;But the hardest thing you&amp;rsquo;ll ever learn is when to leave them broken.&amp;rdquo;&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
