<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Niice Notes</title>
    <link>https://niice.com/blog/notes</link>
    <description>Links, quotes and the occasional thought from the Niice team.</description>
    <language>en</language>
    <lastBuildDate>Sat, 03 Oct 2026 00:00:00 GMT</lastBuildDate>
    <atom:link href="https://niice.com/blog/notes/feed.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Feeding the machine with chaos</title>
      <link>https://niice.com/blog/notes/feeding-the-machine-with-chaos</link>
      <guid isPermaLink="true">https://niice.com/blog/notes/feeding-the-machine-with-chaos</guid>
      <pubDate>Sat, 03 Oct 2026 00:00:00 GMT</pubDate>
      <description><![CDATA[<p><a href="https://automattic.design/2026/10/02/feeding-the-machine-with-chaos/">Feeding the machine with chaos →</a></p>
<blockquote><p>AI is good at extending a system, but it can’t start one. Once the logo was right, everything else could grow from it. But that first decision had to come from someone looking, caring, and crafting.</p></blockquote><p>— Núria Peña, Automattic</p>
<p><img src="https://niice.com/blog/notes/openstation-logo.jpg" alt="How the OpenStation mark was reached: the name shortened to OS, a cloud of sketched O and S variations resolving into a half-filled circle, its phases, and finally a blob mascot with two eyes." /></p><p><em>© Automattic</em></p>
<p>When average is easier than ever, our choices are what set us apart.</p>]]></description>
      <category>Notes</category>
    </item>
    <item>
      <title>Where type comes from</title>
      <link>https://niice.com/blog/notes/where-type-comes-from</link>
      <guid isPermaLink="true">https://niice.com/blog/notes/where-type-comes-from</guid>
      <pubDate>Mon, 21 Sep 2026 00:00:00 GMT</pubDate>
      <description><![CDATA[<p><a href="https://type.lol/studies/where-type-comes-from">Where type comes from →</a></p>
<blockquote><p>Of the 648 designers whose school and workplace have both been identified, 296 work in a different country from the one they trained in. That is 46%. Type design is a field where roughly half the people leave the country that taught them.</p></blockquote><p>— Mark Johnson, Type.lol</p>
<p><img src="https://niice.com/blog/notes/type-lol-migration-globe.png" alt="A globe turned to the Atlantic, threaded with arcs running from where type designers trained to where they now work — a dense knot converging on The Hague and western Europe, with long strands reaching New York, Rio de Janeiro and Buenos Aires." /></p><p><em>© Type.lol</em></p>
<p>Love this deep dive by Mark at Type.lol into the diaspora of the type industry.</p>]]></description>
      <category>Notes</category>
    </item>
    <item>
      <title>How Vercel’s agents build on-brand pages with design.md</title>
      <link>https://niice.com/blog/notes/design-md</link>
      <guid isPermaLink="true">https://niice.com/blog/notes/design-md</guid>
      <pubDate>Wed, 16 Sep 2026 00:00:00 GMT</pubDate>
      <description><![CDATA[<p><a href="https://vercel.com/blog/how-our-agents-build-on-brand-pages-with-design-md">How Vercel’s agents build on-brand pages with design.md →</a></p>
<blockquote><p>The problem we found was that while the prompt described our visual language just fine, every model reading it interpreted that description differently, generating vastly different pages from the same guidance.</p></blockquote><p>— John Phamous, Vercel</p>
<p><img src="https://niice.com/blog/notes/design-md-comparison.jpg" alt="Two very differently styled pages generated from the same prompt, data, model and viewport — one warm and editorial, one cool and data-dense — illustrating how much a model&apos;s output can vary without design.md." /></p><p><em>© Vercel</em></p>
<p>I like Vercel&apos;s approach of running the prompt twice, once with design.md and once without, to compare the impact design.md is actually having.</p>
<p>Right now most of us are still figuring out how to maintain brand consistency across multiple outputs using a single provider of choice (Anthropic/OpenAI). As it becomes more common for orgs to run multiple models—for different tasks and/or teams—we&apos;re going to need more mature ways to evaluate how effectively each model is able to adhere to guidelines.</p>]]></description>
      <category>Notes</category>
    </item>
    <item>
      <title>Authorship Over Output</title>
      <link>https://niice.com/blog/notes/authorship-over-output</link>
      <guid isPermaLink="true">https://niice.com/blog/notes/authorship-over-output</guid>
      <pubDate>Wed, 16 Sep 2026 00:00:00 GMT</pubDate>
      <description><![CDATA[<p><a href="https://brain.co/blog/authorship-over-output">Authorship Over Output →</a></p>
<blockquote><p>We’re eschewing the titles for now (Design Engineer, SuperICs, Principals, Managers, all of them) and calling these roles something Milton Glaser would recognize: Designers.</p>
<p>Our designers are still using AI tools of course, but it doesn’t change their title. We don’t call them Pencil Designers when they sketch on notepads either.</p></blockquote><p>— Shawn Sprockett, Brain Co.</p>
<p>It’s funny how often the best way to face the future is look deeper into the past.</p>]]></description>
      <category>Notes</category>
    </item>
    <item>
      <title>Brand as Software</title>
      <link>https://niice.com/blog/notes/brand-as-software</link>
      <guid isPermaLink="true">https://niice.com/blog/notes/brand-as-software</guid>
      <pubDate>Mon, 14 Sep 2026 00:00:00 GMT</pubDate>
      <description><![CDATA[<p><a href="https://pauljun.substack.com/p/brand-as-software">Brand as Software →</a></p>
<blockquote><p>Highly skilled designers were spending much of their time reproducing decisions the team had already made.</p></blockquote><p>— Paul Jun, Ramp</p>
<p>There’s a lot to unpack in this essay from Paul Jun @ Ramp, but this sentence really jumped out at me. How much of our time is spent being truly creative, versus “lining stuff up”, “spacing things out”, and “fixing the corner radii”?</p>
<p>Machines can do consistency and precision better than us meatbags, but that just gives us more time to focus on what really matters: the <em>why</em>.</p>]]></description>
      <category>Notes</category>
    </item>
    <item>
      <title>Designing with prose</title>
      <link>https://niice.com/blog/notes/designing-with-prose</link>
      <guid isPermaLink="true">https://niice.com/blog/notes/designing-with-prose</guid>
      <pubDate>Wed, 09 Sep 2026 00:00:00 GMT</pubDate>
      <description><![CDATA[<blockquote><p>The power of a language comes from the fact that it is generative. A language is not a mere set of signs, or a set of labels… It is a system of rules, which allows you to create an infinite variety of unique combinations, directly suited to the specific circumstances in which they are used. A drawing cannot do this. A drawing is a picture of one particular thing. It cannot adapt itself.</p></blockquote><p>— Christopher Alexander, <em>The Timeless Way of Building</em>, 1979</p>
<p>These ideas from 50 years ago feel more relevant than ever. I’m finding myself spending less time lining up pixels, and more time thinking about the system of rules that produce those pixels. It’s easy to look at an output and say “that’s the design”, but the design <em>isn’t</em> the output: the design is the <em>choices</em> that led to that output.</p>]]></description>
      <category>Notes</category>
    </item>
  </channel>
</rss>
