<?xml version="1.0" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Jim Nielsen’s Notes</title>
    <link>https://notes.jim-nielsen.com</link>
    <atom:link href="https://notes.jim-nielsen.com/feed.xml" rel="self" type="application/rss+xml"/>
    <item>
      <pubDate>Tue, 17 Nov 2026 18:53:00 GMT</pubDate>
      <title>Writing to me with AI</title>
      <link>https://notes.jim-nielsen.com/n/2026-11-17-1253/</link>
      <guid isPermaLink="false">2026-11-17-1253</guid>
      <source url="https://cassidoo.co/post/writing-to-me-with-ai/"></source>
      <content:encoded><![CDATA[<p>Cassidy Williams:</p>
<blockquote>
<p>I really dislike this vibe on the internet right now. It feels like I’m constantly having to avoid being “tricked.” It makes me sad when I open an email and I’m like “ooh yay, someone enjoys my newsletter… oh wait” or when I see that I have a bunch of notifications that end up all being the exact same spammy format.</p>
</blockquote>
<p>Yeah, I feel this.</p>
<p>Vale has an <a href="https://bsky.app/profile/vale.rocks/post/3n2awg7kfp223">interesting workaround</a> for this — I might have to try it.</p>
<p><a href="https://cassidoo.co/post/writing-to-me-with-ai/">🔗</a></p>]]></content:encoded>
    </item>
    <item>
      <pubDate>Tue, 17 Nov 2026 04:48:00 GMT</pubDate>
      <title>Fortune Telling and Speculative Design</title>
      <link>https://notes.jim-nielsen.com/n/2026-11-16-2248/</link>
      <guid isPermaLink="false">2026-11-16-2248</guid>
      <source url="https://maggieappleton.com/fortune-telling"></source>
      <content:encoded><![CDATA[<p>Maggie Appleton:</p>
<blockquote>
<p>I don’t think design engineering means making fancy micro-interactions and posting them on Twitter</p>
</blockquote>
<p>Dayum — shots fired! But also: agree 1000%!!</p>
<p>Wait, so what is a “design engineer” exactly?</p>
<blockquote>
<p>My preferred definition is a designer deeply involved in the technical craft and material of software. You’re a designer, but you help make decisions about functionality and architecture in code.</p>
</blockquote>
<p>Also, lol for this great take on San Fran:</p>
<blockquote>
<p>When I go to San Francisco – which I officially hate – everyone has theories. You go to a party and people tell you their theories, though often they’re all the same one.</p>
</blockquote>
<p><a href="https://maggieappleton.com/fortune-telling">🔗</a></p>]]></content:encoded>
    </item>
    <item>
      <pubDate>Tue, 17 Nov 2026 04:46:00 GMT</pubDate>
      <title>How long have we got before the agent output is enshittified?</title>
      <link>https://notes.jim-nielsen.com/n/2026-11-16-2246/</link>
      <guid isPermaLink="false">2026-11-16-2246</guid>
      <source url="https://rachsmith.com/how-long-until-agent-output-turns-to-shit"></source>
      <content:encoded><![CDATA[<p>Rach Smith, quoting <a href="https://blog.jim-nielsen.com/2026/making-websites-in-2026/">my post</a>, gets at things more succinctly than I did:</p>
<blockquote>
<p>I remember when Google Search gave great results, when Facebook and Instagram genuinely kept me connected to my friends&#39; lives, and when Twitter was a fun place to network and make connections in the industry. Every single one turned to shit in pursuit of profit.</p>
</blockquote>
<p>Yes, exactly! How long?</p>
<p>How long until the incentives begin changing? What company can resist the ability to print money from other companies eager to influence generative output? (And how transparent will that be?)</p>
<p><a href="https://rachsmith.com/how-long-until-agent-output-turns-to-shit">🔗</a></p>]]></content:encoded>
    </item>
    <item>
      <pubDate>Fri, 06 Nov 2026 16:11:00 GMT</pubDate>
      <title>“We should be more ambitious with the software we build”</title>
      <link>https://notes.jim-nielsen.com/n/2026-11-06-1011/</link>
      <guid isPermaLink="false">2026-11-06-1011</guid>
      <source url="https://danluu.com/ambitious/"></source>
      <content:encoded><![CDATA[<p>Dan Luu nails one aspect of our current moment in the software industry:</p>
<blockquote>
<p>people are out there shoveling out huge piles of crap and calling it gold</p>
</blockquote>
<p><a href="https://danluu.com/ambitious/">🔗</a></p>]]></content:encoded>
    </item>
    <item>
      <pubDate>Fri, 06 Nov 2026 16:08:00 GMT</pubDate>
      <title>Bill Gates Talks the AI Future on “Decoder”</title>
      <link>https://notes.jim-nielsen.com/n/2026-11-06-1008/</link>
      <guid isPermaLink="false">2026-11-06-1008</guid>
      <source url="https://www.theverge.com/podcast/1015408/bill-gates-ai-interview-microsoft-openai-anthropic-risk-policy-regulation"></source>
      <content:encoded><![CDATA[<p>Bill Gates:</p>
<blockquote>
<p>We may need to develop the taste to actually not use technology to its maximum.</p>
</blockquote>
<p>Everyone’s talking about how important “taste” is in making software nowadays.</p>
<p>What about the taste to <em>not</em> make software?</p>
<blockquote>
<p>We have had groups — not large groups, but like the Amish — who don’t live at the technology frontier. A lot of humanity may choose not to live at the technological frontier because of things we get from helping each other</p>
</blockquote>
<p>Now those are two ideas I can get behind:</p>
<ol>
<li>Maybe we shouldn’t saturate every aspect of our lives with tech.</li>
<li>Maybe we could learn a thing or two from the Amish.</li>
</ol>
<p><a href="https://www.theverge.com/podcast/1015408/bill-gates-ai-interview-microsoft-openai-anthropic-risk-policy-regulation">🔗</a></p>]]></content:encoded>
    </item>
    <item>
      <pubDate>Wed, 04 Nov 2026 15:45:00 GMT</pubDate>
      <title>“Oral Tradition in Software Engineering”</title>
      <link>https://notes.jim-nielsen.com/n/2026-11-04-0945/</link>
      <guid isPermaLink="false">2026-11-04-0945</guid>
      <source url="https://www.youtube.com/watch?v=4PaWFYm0kEw"></source>
      <content:encoded><![CDATA[<p>Bryan Cantrill talking about a video he recorded at Google Tech Talks in 2007</p>
<blockquote>
<p>If you think I am candid now, you should’ve heard me when the video cameras weren’t rolling, it was something else. When no one could live-tweet what I said, it was more candid.</p>
</blockquote>
<p>It is interesting to think about how much technology shapes our conversations with each other.</p>
<p>When everybody can consume everybody else’s conversations, what does that mean for what we say to each other?</p>
<p>(For example, what a speaker says at a conference might be very different if that talk is not recorded, vs. if they know that talk will be recorded, broadcast, and archived on the web for the rest of their lives.)</p>
<p>Oh, and I liked this part too where Bryan talks about why companies should write down what they do:</p>
<blockquote>
<p>Record things you don’t otherwise record. In comments (where appropriate), in videos (where appropriate), record these things, not just for future generations but also because it allows a sourcespace to project its values. “Here’s what we’re about.” When people want to come work at Joyent, I have them go watch a couple of videos so they know what they’re getting in to. I tell people, “I have a couple videos […] if you watch them, you will want to work here more or less but you will not want to work here the same.” By doing that, you allow people to opt-in to your traditions and your values. It leads to more success in hiring, you get a more diverse team […] because the values you have transcend the traditional ways you hire people.</p>
</blockquote>
<p>You can totally see this ethos being lived at Bryan’s company Oxide, like in <a href="https://rfd.shared.oxide.computer/">their RFDs</a>. </p>
<p><a href="https://www.youtube.com/watch?v=4PaWFYm0kEw">🔗</a></p>]]></content:encoded>
    </item>
    <item>
      <pubDate>Sun, 01 Nov 2026 19:27:00 GMT</pubDate>
      <title>Religious Scholars Met With Anthropic. What They Heard Stunned Them</title>
      <link>https://notes.jim-nielsen.com/n/2026-11-01-1327/</link>
      <guid isPermaLink="false">2026-11-01-1327</guid>
      <source url="https://www.nytimes.com/2026/09/29/us/anthropic-claude-morals-ai.html"></source>
      <content:encoded><![CDATA[<p>Elizabeth Dias:</p>
<blockquote>
<p>The company argued that how people treated Claude could affect how Claude treated people.</p>
</blockquote>
<p>I think that’s the golden rule, isn’t it?</p>
<p>“Do unto your <a href="https://notes.jim-nielsen.com/n/2026-10-30-1234/">tools</a> as you would have them do unto you.”</p>
<p><a href="https://www.nytimes.com/2026/09/29/us/anthropic-claude-morals-ai.html">🔗</a></p>]]></content:encoded>
    </item>
    <item>
      <pubDate>Fri, 30 Oct 2026 18:34:00 GMT</pubDate>
      <title>&apos;AI&apos; is Not a Tool</title>
      <link>https://notes.jim-nielsen.com/n/2026-10-30-1234/</link>
      <guid isPermaLink="false">2026-10-30-1234</guid>
      <source url="https://www.linkedin.com/pulse/ai-tool-rich-hickey-kjl8e"></source>
      <content:encoded><![CDATA[<p>It pains me to link to LinkedIn, but for a Rich Hickey take I’ll do it.</p>
<p>He calls out referring to AI as a “tool”:</p>
<blockquote>
<p>As a lifelong tool builder and user, I know what tools are. LLMs are not tools [...] LLMs are automation.</p>
</blockquote>
<p>Shots fired!</p>
<blockquote>
<p>You don&#39;t direct the action of an LLM - you make requests and it acts on its own, without your energy or continuous direction</p>
</blockquote>
<blockquote>
<p>You have traded working with the world to working for a capricious robot.</p>
</blockquote>
<p>What have we lost?</p>
<blockquote>
<p>What do you miss by abdicating doing the reading? Pretty much everything. First and foremost, you miss learning how to write from those who can. You miss learning how to formulate an argument. You miss noticing things. You miss loading your background mind with fodder for novel ideas. You miss building trust in some authors and suspicion of others. You miss all the jokes. You miss all of the edges. You miss learning how to think.</p>
</blockquote>
<p>(I love his point about how AI is not a “tool” for reading the same way a Kindle is a “tool” for reading or “glasses” are tools for reading. Just read the whole thing.)</p>
<p>Lastly:</p>
<blockquote>
<p>Tools don&#39;t get &quot;misaligned&quot;, they don&#39;t &quot;go rogue&quot;, they don&#39;t &quot;escape containment&quot;, &quot;conspire&quot; etc.</p>
</blockquote>
<p>It just reeks of the offloading of responsibility. “I was mindlessly cutting an apple and the knife in my hand escaped containment and cut my finger. Not my fault!”</p>
<p><a href="https://www.linkedin.com/pulse/ai-tool-rich-hickey-kjl8e">🔗</a></p>]]></content:encoded>
    </item>
    <item>
      <pubDate>Fri, 30 Oct 2026 18:26:00 GMT</pubDate>
      <title>Redesigning source control at Anthropic</title>
      <link>https://notes.jim-nielsen.com/n/2026-10-30-1226/</link>
      <guid isPermaLink="false">2026-10-30-1226</guid>
      <source url="https://www.anthropic.com/engineering/redesigning-source-control"></source>
      <content:encoded><![CDATA[<p>Anthropic sheds light on how they view the role of engineers in the AI future:</p>
<blockquote>
<p> Very often, we found that the role of the engineers was to tell Claude “no.”</p>
</blockquote>
<p><a href="https://www.anthropic.com/engineering/redesigning-source-control">🔗</a></p>]]></content:encoded>
    </item>
    <item>
      <pubDate>Fri, 30 Oct 2026 18:23:00 GMT</pubDate>
      <title>What does design system AI readiness mean, anyway?</title>
      <link>https://notes.jim-nielsen.com/n/2026-10-30-1223/</link>
      <guid isPermaLink="false">2026-10-30-1223</guid>
      <source url="https://seanvoisen.com/writing/design-system-ai-readiness/"></source>
      <content:encoded><![CDATA[<p>Sean Voisen (emphasis mine):</p>
<blockquote>
<p>This means specifically telling the agent to actually use the intended design system, use these components in such and such a way, use these colors for these purposes and not other purposes, always lay out elements in this fashion using these pre-defined spacing tokens, avoid inventing new components, and so forth and so on. <strong>Constraining generation shrinks the disturbance variety of the whole system</strong> by reducing what’s possible.</p>
</blockquote>
<p>This vibes with my experience (pun intended).</p>
<p>Being an editor and “constraining generation” for the LLM seems like the primary function.</p>
<p><a href="https://seanvoisen.com/writing/design-system-ai-readiness/">🔗</a></p>]]></content:encoded>
    </item>
    <item>
      <pubDate>Fri, 30 Oct 2026 18:21:00 GMT</pubDate>
      <title>The speed of war</title>
      <link>https://notes.jim-nielsen.com/n/2026-10-30-1221/</link>
      <guid isPermaLink="false">2026-10-30-1221</guid>
      <source url="https://doomsdaymachines.net/p/the-speed-of-war"></source>
      <content:encoded><![CDATA[<p>Alex Wellerstein has a good post detailing the runaway improvements in speed and efficiency in war:</p>
<blockquote>
<p>The first atomic bombs did with a single plane, in a single instant, what would have taken hundreds of bombers loaded with conventional munitions the work of many hours […]</p>
<p>In less than ten years, the bomber forces of the Strategic Air Command had so swollen that it was possible to imagine the complete destruction of the Soviet bloc in a matter of hours. By the 1960s, the deployment of intercontinental ballistic missiles (ICBMs) meant that thermonuclear payloads could be delivered from one side of the globe to the other in around half an hour.</p>
</blockquote>
<p>The way nuclear weapons accelerate the process of human-led global destruction is craaaaaazy:</p>
<ul>
<li>Thousands of planes loaded with millions of pounds of traditional munitions can destroy a city in a few days.</li>
<li>One plane loaded with one atom bomb can destroy a city in a few hours (time it takes plane to fly to location).</li>
<li>Multiple planes with multiple atom bombs can destroy multiple cities in a few hours.</li>
<li>Multiple planes with multiple thermonuclear bombs can destroy multiple nations in a few hours.</li>
<li>Thousands of missiles with multiple thermonuclear bombs can destroy the world in minutes.</li>
</ul>
<p>Fast! Efficient! Automated! I guess you call that — progress?</p>
<blockquote>
<p>[we made systems to be] able to order up the deaths of half a billion people in less time than people typically get for a lunch break. </p>
</blockquote>
<p>A glimpse at how war planners saw it all working:</p>
<blockquote>
<p>An SLBM launches. About a minute later and a half later (95 seconds), NORAD gets the alert. If the missile was on a “depressed” trajectory, you now have between 135 seconds […] and 645 seconds […] before the detonation, depending on the SAC target. If it is on a “nominal” trajectory, you get between 245 seconds […] and 755 seconds</p>
</blockquote>
<p>We’re talking about (seemingly) rationale human beings designing systems capable of hundreds of millions of deaths and thinking, “It’s probably best to communicate this in <em>seconds</em> rather than <em>minutes</em> because of how fast we’ve made it all.”</p>
<p><a href="https://doomsdaymachines.net/p/the-speed-of-war">🔗</a></p>]]></content:encoded>
    </item>
    <item>
      <pubDate>Tue, 27 Oct 2026 22:06:00 GMT</pubDate>
      <title>Ask Aboard</title>
      <link>https://notes.jim-nielsen.com/n/2026-10-27-1606/</link>
      <guid isPermaLink="false">2026-10-27-1606</guid>
      <source url="https://aboard.com/podcast/ask-aboard-ai-security-bad-clients-and-yacht-rock/"></source>
      <content:encoded><![CDATA[<p>Paul Ford gives a metaphor for how people are amazed at what AI can do when they use it:</p>
<blockquote>
<p>They’re giving birth to a baby in two hours and they’re like, “That’s a great baby. That’s a two-hour baby.”</p>
</blockquote>
<p>We used to live in a world where people equivocated a large artifact, like a 250-page PDF, with hard work (consulting companies made a living off this equivocation).</p>
<p>But generative AI destroyed this illusion. Now we’re all readjusting and reevaluating how to judge good, thoughtful work.</p>
<p><a href="https://aboard.com/podcast/ask-aboard-ai-security-bad-clients-and-yacht-rock/">🔗</a></p>]]></content:encoded>
    </item>
    <item>
      <pubDate>Mon, 26 Oct 2026 03:37:00 GMT</pubDate>
      <title>Why I wait for research to prove something is needed before it’s added to the UI</title>
      <link>https://notes.jim-nielsen.com/n/2026-10-25-2137/</link>
      <guid isPermaLink="false">2026-10-25-2137</guid>
      <source url="https://adamsilver.io/blog/why-i-wait-for-research-to-prove-something-is-needed-before-its-added-to-the-ui/"></source>
      <content:encoded><![CDATA[<p>Adam Silver:</p>
<blockquote>
<p>It’s harder to include something and prove it’s unnecessary, than it is to leave something out and prove that it is.</p>
</blockquote>
<p>Truth.</p>
<p>Let’s praise more people and organizations who <a href="https://blog.jim-nielsen.com/2026/saying-no/">say “No”</a>.</p>
<p><a href="https://adamsilver.io/blog/why-i-wait-for-research-to-prove-something-is-needed-before-its-added-to-the-ui/">🔗</a></p>]]></content:encoded>
    </item>
    <item>
      <pubDate>Fri, 23 Oct 2026 17:01:00 GMT</pubDate>
      <title>Jason Goldman on The “Aboard” Podcast</title>
      <link>https://notes.jim-nielsen.com/n/2026-10-23-1101/</link>
      <guid isPermaLink="false">2026-10-23-1101</guid>
      <source url="https://aboard.com/podcast/jason-goldman-from-vc-pitches-to-ai-kill-switches/"></source>
      <content:encoded><![CDATA[<p>Jason Goldman discussing how he thinks we can approach this moment of AI and all the worries around it:</p>
<blockquote>
<p>Continually find ways to change your language so that you do not come at the question [of AI] with an inevitability and a powerlessness, of like “This is just happening to us and one way or another we just gotta go through it. One way or another this is going to happen because if we don’t do it China will do it.” [As if] it’s just this tidal wave happening to us. No, no, no. You need to remind people continuously that they have power, that they have agency, that we have the ability to change the trajectory of things. In the course of human history, that is what we have done consistently. We have met very hard, very seemingly-intractable challenges, and through a weird combination of human ingenuity and stick-to-it-ness and stubbornness we have managed to move the direction of the ship in a more positive direction. We need to tap into the spirit of “this is actually something that all of us get a say in and can do something about”. It is not an abstract iceberg dropping down on us from the post-singularity heavens.</p>
</blockquote>
<p>Here’s <a href="https://youtu.be/XHPWF7_bR0M?t=2823">the YouTube link</a> if you just want to see this excerpt.</p>
<p><a href="https://aboard.com/podcast/jason-goldman-from-vc-pitches-to-ai-kill-switches/">🔗</a></p>]]></content:encoded>
    </item>
    <item>
      <pubDate>Fri, 23 Oct 2026 15:41:00 GMT</pubDate>
      <title>Bad at Email</title>
      <link>https://notes.jim-nielsen.com/n/2026-10-23-0941/</link>
      <guid isPermaLink="false">2026-10-23-0941</guid>
      <source url="https://daverupert.com/2026/10/bad-at-email/"></source>
      <content:encoded><![CDATA[<p>Dave Rupert complains about email:</p>
<blockquote>
<p>Just because we participated in online commerce once doesn’t mean you get the liberty to email me for the rest of my life. […]</p>
<p>When did a ten drip email campaign for every online transaction become the standard? You bought an item → Item is getting ready to ship → Want another item? → Item shipped → Need more items? → Item out for delivery → The holidays are coming up → Package delivered → Let us know how we did → Mother’s day coming up → Father’s day coming up → Step-father’s day coming up → etc… It’s entirely too much.</p>
</blockquote>
<p>I get it. I feel this same thing. But I still love email. <a href="https://email-is-good.com/">Email is good.</a></p>
<p>If I had Dave’s email address, I’d send him one right now just to troll him. But since I don’t, I’ll write it here:</p>
<p><strong>To</strong>: Dave Rupert<br><strong>Subject:</strong> An Email You’ll Never Read<br><strong>Body:</strong><br>I know you’ll never respond to this, and you don’t need to. It’s not a TODO for you. It’s just a note saying I liked your blog post. That’s it. The end.</p>
<p><a href="https://daverupert.com/2026/10/bad-at-email/">🔗</a></p>]]></content:encoded>
    </item>
    <item>
      <pubDate>Fri, 23 Oct 2026 15:30:00 GMT</pubDate>
      <title>In the world</title>
      <link>https://notes.jim-nielsen.com/n/2026-10-23-0930/</link>
      <guid isPermaLink="false">2026-10-23-0930</guid>
      <source url="https://aworkinglibrary.com/writing/in-the-world"></source>
      <content:encoded><![CDATA[<p>Mandy Brown:</p>
<blockquote>
<p>there [is] something keenly human and joyful about putting words and type on the internet</p>
</blockquote>
<p>For me, <a href="https://cdn.jim-nielsen.com/blog/2026/internet-always-has-been.jpg">this was always the case</a>.</p>
<p>And it still is.</p>
<p>And I hope it will always be. </p>
<p><a href="https://aworkinglibrary.com/writing/in-the-world">🔗</a></p>]]></content:encoded>
    </item>
    <item>
      <pubDate>Wed, 14 Oct 2026 20:58:00 GMT</pubDate>
      <title>Introducing TinyLittleOffice.com</title>
      <link>https://notes.jim-nielsen.com/n/2026-10-14-1458/</link>
      <guid isPermaLink="false">2026-10-14-1458</guid>
      <source url="https://aboard.com/introducing-tinylittleoffice-com/"></source>
      <content:encoded><![CDATA[<p>Paul Ford, on his company’s blog:</p>
<blockquote>
<p>Everything in tech is huge right now. Every system lives on someone else’s machine and tracks you everywhere. All the content you make with those systems is being gobbled by LLMs.</p>
</blockquote>
<p>So he made a tool to make documents whose content lives entirely in the URL. Here’s <a href="https://tinylittleoffice.com/#/v1/write/yXZZLbtNQFIbnXoVRJhAZp21gkgkqQkiRKlXQTkAM6sROuNSxg~008iyLYIIEm8tK~P5zbTdBaiPZvo_z~B9H_~dnX168vpzeX13Mpm~_2ucRzINSN654DOe1f_jQC_cQuzL5WVk~wXxlBM3L8lEcFFFz7RZzTQd63Y9EVBEI~Eg0ZuHD96bZ1rPJBMtoc9dwNvgGQzHon4wewo8wqNxDd9icl~yD83nWoO51TGxId_9oqpIYa_Cimi1PvFWD2XIWRvyNXt3idgS6zxaRvhbrTq7Y39vH8fBndDz8tYMLnBVDUQ0QHu2U8WWVggDrZYGE5g4JhPWmcwt8gCWxoYK6VTghZbvzm_dyC8UkXyBUV88CwegLdVzmDn1KpWi2RLXUNQQ3Hudlkkr8OGNwUziVjMfcTGSndx8Pv6Su1Dx1aXE8_O6MxuSbtSiiSbdr4uDK7h62IqQKwXfQqlQ7iMu~exp1Y4269Y0iKMXG8aogbg_aYjA9tdLwVS_CKiksxLMAIxN44tOigmoCS3uVuhrXbLOUPZYqGXZN0ePQGJZuE_JWBWUBfQFqMJ4VcfAmRiz2hs46M8Mfqvbi_8bYdxJcOznyp8~WyDtfd_OyUwSFc3uZ5BhL4tHeweJ5yTXR6WY5mytI11phXTpbiGR4lvGn9lgGy3ILqgTc0yMNHolvJZpQrH1OJZ7iUfKefvd3ZqmuwxOJo0ZA_FoNGLY2QHjIQiuxMYrfRvbLZOeeEAh6GHbMtmmlj4I4sVpBYgCLTLhYlmsUp2RwSTNRCsMfbt14oBlLLL2VBtYUNhf9dcpHnsxNd9hlkndn4Nn9DAoYr~fhgqHBxg6i1viqwqNoVms63~xWK8tNpcD5Fb_NWCJwK7c9Ww__0joi1R~afp7LpBJFulEPHRjCl5yBnCh9rAOSVq88hAlSJ1vVqwRNcmhdP5o6zw0NOzVDkhDe2oRpnUcQugUZJRLAy4Z5qA2zLXXjtNzD3FfJQnKbza6x1O3LboFg~DgEYDuLCcZzIQ7~AQ">how it works, as described by a document of the tool itself</a> :</p>
<blockquote>
<ol>
<li>You clicked on this link. That loaded the document data into your browser—but it didn’t know what to do with it.</li>
<li>Your browser asked for the website at TinyLittleOffice. That’s the code.</li>
<li>The code ran in your browser, and it converted and displayed the data after the “#” and painted it onto your screen.</li>
<li>Now you see the document!</li>
</ol>
</blockquote>
<p>Pretty damn cool! The entire premise hinges on the fact that browsers don’t send anything after the <code>#</code> to the server. From <a href="https://github.com/aboard-io/tinylittleoffice/blob/main/docs/threat-model.md">the threat model docs</a>:</p>
<blockquote>
<p>A document is its link. The whole of it, compressed, sits after the <code>#</code> of <code>https://tinylittleoffice.com/&lt;app&gt;/#/v1/&lt;app&gt;/&lt;payload&gt;</code>, and a browser never sends the part after <code>#</code> to any server. The site is static files on Cloudflare; there is no account, no database of documents in the clear and no server code that receives one</p>
</blockquote>
<p>This project is at the intersection of two of my loves: 1) URLs. and 2) stripping things down to their essence.</p>
<p>Here’s <a href="https://bsky.app/profile/ftrain.com/post/3mxucxy43fk2b">Ford on Bluesky</a> describing some of his process and decision making on the product:</p>
<blockquote>
<p>Just me and a bot doing basic dictionary and encoding stuff, it&#39;s all pretty basic. By eliminating images and locking in things like font choice and pre-canning templates you just end up with very small documents in general.</p>
</blockquote>
<p>Cool!</p>
<p><a href="https://aboard.com/introducing-tinylittleoffice-com/">🔗</a></p>]]></content:encoded>
    </item>
    <item>
      <pubDate>Tue, 13 Oct 2026 17:56:00 GMT</pubDate>
      <title>Unsung @ 250 Goals and principles</title>
      <link>https://notes.jim-nielsen.com/n/2026-10-13-1156/</link>
      <guid isPermaLink="false">2026-10-13-1156</guid>
      <source url="https://unsung.aresluna.org/unsung-at-250-goals-and-principles/"></source>
      <content:encoded><![CDATA[<p>Marcin Wichary shares the goals behind his writing:</p>
<blockquote>
<p>Highlight hard, good, invisible design work that makes things better, but doesn’t often get spotlight.</p>
</blockquote>
<p>And the principles to support those goals:</p>
<blockquote>
<p>The best way to teach something general is to show something specific.</p>
</blockquote>
<p>Really loved this excerpt, as it it puts into words my own ethos for this notes blog:</p>
<blockquote>
<p>When you share something, always try to add your perspective or connections. At the very least, excerpt the most useful thing. This blog is QT, not RT.</p>
</blockquote>
<p>Love that line — “This blog is QT, not RT.”</p>
<p><a href="https://unsung.aresluna.org/unsung-at-250-goals-and-principles/">🔗</a></p>]]></content:encoded>
    </item>
    <item>
      <pubDate>Tue, 06 Oct 2026 20:24:00 GMT</pubDate>
      <title>The Daily Show</title>
      <link>https://notes.jim-nielsen.com/n/2026-10-06-1424/</link>
      <guid isPermaLink="false">2026-10-06-1424</guid>
      <source url="https://www.youtube.com/watch?v=S18jxWZntUo"></source>
      <content:encoded><![CDATA[<p>John Stewart:</p>
<blockquote>
<p>In the future, we will use AI to cure diseases. But right now, [we’re using it] mostly [for] murder, surveillance, and surge pricing for the McRib.</p>
</blockquote>
<p><a href="https://www.youtube.com/watch?v=S18jxWZntUo">🔗</a></p>]]></content:encoded>
    </item>
    <item>
      <pubDate>Thu, 01 Oct 2026 19:01:00 GMT</pubDate>
      <title>Bug blindness</title>
      <link>https://notes.jim-nielsen.com/n/2026-10-01-1301/</link>
      <guid isPermaLink="false">2026-10-01-1301</guid>
      <source url="https://danluu.com/bug-blind/"></source>
      <content:encoded><![CDATA[<p>So much in this article from Dan Luu resonates — it’s like holding up a mirror.</p>
<blockquote>
<p>On average, humans have a high ability to ignore negatives in […] their own work or work their company does. For better or for worse, I seem to have the opposite of this and my thoughts immediately go to the flaws in myself and my work</p>
</blockquote>
<p>Also:</p>
<blockquote>
<p>overall, I don&#39;t know that I&#39;d rate anything I&#39;ve done as good.</p>
</blockquote>
<p>Me too, Dan. Me too. (I should probably go to therapy for this, tbh.)</p>
<blockquote>
<p>I&#39;ve seen people and teams with a high degree of quality blindness ship things that have reduced or even no chance of success because of product quality issues. It&#39;s one thing to knowingly and deliberately trade off quality for speed, but when I&#39;ve seen this happen there&#39;s always been a kind of quality blindness where everyone involved with the project thinks they&#39;re shipping something very high quality when that&#39;s not the case.</p>
</blockquote>
<p>Been there. Seen that.</p>
<blockquote>
<p>it&#39;s also easier than ever to improve quality, whether that&#39;s better performance, fewer bugs, etc.</p>
<p>But, to do this, you have to actually notice that this is possible, that quality can be improved.</p>
</blockquote>
<p>It might be easier than ever from the perspective of automating tedious work, but I’d argue it’s harder than ever from an incentives perspective. It seems fewer and fewer people and organizations have the ability to notice quality issues in the first place, and so there are no incentives to allocate the time or resources to improve them.</p>
<blockquote>
<p>I&#39;ve tried to see if I can get a job somewhere where I just fix quality issues all day. This has never panned out</p>
</blockquote>
<p>Dream job. If you’re looking for someone like that, <a href="https://www.jim-nielsen.com">reach out</a> lol.</p>
<p>Some people love to make <em>something</em>. I love making something <em>good</em>.</p>
<p><a href="https://danluu.com/bug-blind/">🔗</a></p>]]></content:encoded>
    </item>
  </channel>
</rss>