<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Jason Sanzone · Journal</title>
    <link>https://sanz.one/journal/</link>
    <description>Jason Sanzone on design, AI, EDC and gear, and everything else.</description>
    <language>en-us</language>
    <lastBuildDate>Wed, 07 Oct 2026 00:00:00 GMT</lastBuildDate>
    <atom:link href="https://sanz.one/journal/feed.xml" rel="self" type="application/rss+xml"/>
    <item>
      <title>The Formula Nobody Puts on a Resume</title>
      <link>https://sanz.one/journal/the-formula-nobody-puts-on-a-resume/</link>
      <guid isPermaLink="true">https://sanz.one/journal/the-formula-nobody-puts-on-a-resume/</guid>
      <pubDate>Wed, 07 Oct 2026 00:00:00 GMT</pubDate>
      <description>Obsession, pattern recognition, zero deference, and delusional optimism look like red flags. They&#39;re more like a stack.</description>
      <content:encoded><![CDATA[<p>Obsession. Pattern recognition. Zero deference. Delusional optimism.</p>
<p>Most people treat those like red flags. They&#39;re more like a stack.</p>
<p>You stare at the same problem until the pattern shows up. You skip the polite version. You keep going past the point where a normal person would call it done and ask for feedback. From the outside it looks unhinged. From the inside it just looks like refusing to settle for fine.</p>
<p>AI can do the first draft. It can&#39;t do that stack. That&#39;s still on you.</p>
]]></content:encoded>
    </item>
    <item>
      <title>Caring Too Much Is Underrated</title>
      <link>https://sanz.one/journal/caring-too-much-is-underrated/</link>
      <guid isPermaLink="true">https://sanz.one/journal/caring-too-much-is-underrated/</guid>
      <pubDate>Tue, 29 Sep 2026 00:00:00 GMT</pubDate>
      <description>Taste is deciding to keep looking after everyone else has moved on, and AI just made that more valuable.</description>
      <content:encoded><![CDATA[<p>Most people call it obsessing. Spending another hour on a button that already works. Moving a label two pixels because something felt off and you couldn&#39;t leave it alone. I do that a lot. I&#39;m not embarrassed by it.</p>
<p>Taste isn&#39;t a gift you either have or don&#39;t. It&#39;s deciding to keep looking after everyone else has moved on. The first version of almost anything is fine. The tenth version is where it starts to feel like someone cared. The twentieth is where strangers notice without knowing why.</p>
<p>That matters more now than it ever has. AI can spit out a screen in seconds, and most of it looks fine. Fine is everywhere. The difference between fine and good is still someone sitting with it longer than the model did, noticing what it got wrong, and iterating until it feels inevitable.</p>
<p>Half of good UI is work you never show anyone. You try the spacing, hate it, try again, hate that too, and eventually land on something that looks like it was always meant to be that way. Nobody sees the twenty versions that died. They just feel the one that didn&#39;t.</p>
<p>The work is quiet and a little lonely. You notice the alignment nobody else will mention. You kill the clever idea that looked cool for five minutes. That last part is the hard one. Taste is also knowing when to stop polishing and ship.</p>
<p>If you&#39;re the person who can&#39;t leave a screen alone, keep going. That itch is the whole job, and the tools just made it more valuable.</p>
]]></content:encoded>
    </item>
    <item>
      <title>Size Isn&#39;t Everything</title>
      <link>https://sanz.one/journal/size-isnt-everything/</link>
      <guid isPermaLink="true">https://sanz.one/journal/size-isnt-everything/</guid>
      <pubDate>Mon, 28 Sep 2026 00:00:00 GMT</pubDate>
      <description>Why small teams with good tools and good taste are about to beat the big ones.</description>
      <content:encoded><![CDATA[<p>Headcount used to be how a company showed it was serious. Want to build something big? Hire a building&#39;s worth of people and buy a ping-pong table nobody uses. I don&#39;t think that works anymore.</p>
<p>Building Overskill, I watch things that used to take a sprint get done in an afternoon. When making things gets that cheap, having lots of people who make things stops being the advantage. What matters is knowing what to make and caring enough to make it well.</p>
<p>Big teams pay for coordination: meetings, docs, planning cycles, and a meeting to plan the next meeting. Small teams skip most of that. The person with the idea builds it, ships it, and reads the first angry email about it.</p>
<p>Taste is the new bottleneck, and it doesn&#39;t scale with headcount. Committees are where good ideas go to die slowly, surrounded by stakeholders who never visit.</p>
<p>A small team can hear from a customer in the morning and ship a fix by lunch. The big competitor is still trying to find a conference room that&#39;s free on Thursday.</p>
<p>If you&#39;re small, stop treating your size as something to grow out of. Use the tools hard, hire only for leverage or judgment you don&#39;t have, and keep the path from idea to shipped short.</p>
<p>The next great companies will look tiny. The big ones will look surprised.</p>
]]></content:encoded>
    </item>
  </channel>
</rss>
