<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <title>Robert A. Paauwe</title>
  <subtitle>Design + System Thinking + Platforms + Complex Orgs</subtitle>
  <link href="https://robertpaauwe.com/atom.xml" rel="self" type="application/atom+xml" />
  <link href="https://robertpaauwe.com/" rel="alternate" type="text/html" />
  <id>https://robertpaauwe.com/</id>
  <updated>2026-11-10T00:00:00.000Z</updated>
  <author>
    <name>Robert A. Paauwe</name>
    <uri>https://robertpaauwe.com/about/</uri>
  </author>
  <entry>
    <title>‘Fine’ will be the new terrible</title>
    <link href="https://robertpaauwe.com/blog/fine-will-be-the-new-terrible/" rel="alternate" type="text/html" />
    <id>https://robertpaauwe.com/blog/fine-will-be-the-new-terrible/</id>
    <published>2026-11-10T00:00:00.000Z</published>
    <updated>2026-11-10T00:00:00.000Z</updated>
    <summary>When everybody can produce the same slop, great has to come from somewhere else.</summary>
    <category term="design-leadership" />
    <category term="ai" />
    <content type="html">&lt;p&gt;If you work in design in a large organization, you’ve probably experienced the following by now. Over the weekend, a product manager did some “experimenting” with Claude, and on Monday there’s a link in the team channel. A working prototype. You don’t hate it. You don’t love it either. It’s fine, the same way a hotel room is ‘fine’.&lt;/p&gt;
&lt;p&gt;So if anyone can produce something ‘fine’ in 10 minutes, what is the point of a designer?&lt;/p&gt;
&lt;h2 id=&quot;01-being-a-maker-used-to-be-mandatory&quot;&gt;&lt;span&gt;01&lt;/span&gt; Being a maker used to be mandatory&lt;/h2&gt;
&lt;p&gt;Creating things used to be design’s territory. Now anyone can produce something, whether or not they have the knowledge. In itself, that’s great. A prototype is a good starting point for discussion.&lt;/p&gt;
&lt;p&gt;The problem is that rough work used to show that the thinking wasn’t finished, and enabled deeper thinking. One of my first design teachers once told me:&lt;/p&gt;
&lt;figure&gt; &lt;blockquote&gt; &lt;p&gt;Draw it really poorly, so people talk about the quality of your idea, not the quality of your drawing.&lt;/p&gt; &lt;/blockquote&gt;  &lt;/figure&gt;
&lt;p&gt;Generated work is never rough. It’s polished. It &lt;em&gt;feels&lt;/em&gt; finished even though it could be just a sketch. The people who made it often can’t articulate what’s wrong with it, or why certain elements work.&lt;/p&gt;
&lt;figure&gt; &lt;div&gt; &lt;div&gt; &lt;img src=&quot;https://robertpaauwe.com/_astro/fine-will-be-the-new-terrible-generated-designs.BKTmfGDS_27274R.webp&quot; srcset=&quot;https://robertpaauwe.com/_astro/fine-will-be-the-new-terrible-generated-designs.BKTmfGDS_edds0.webp 400w, https://robertpaauwe.com/_astro/fine-will-be-the-new-terrible-generated-designs.BKTmfGDS_18RpVX.webp 600w, https://robertpaauwe.com/_astro/fine-will-be-the-new-terrible-generated-designs.BKTmfGDS_1xmKDq.webp 900w, https://robertpaauwe.com/_astro/fine-will-be-the-new-terrible-generated-designs.BKTmfGDS_S4mX3.webp 1200w&quot; alt=&quot;I’ve generated these in 10 minutes, based on a screenshot of my banking app&quot; sizes=&quot;(min-width: 812px) 812px, 100vw&quot; width=&quot;3200&quot; height=&quot;1800&quot;&gt; &lt;/div&gt; &lt;/div&gt; &lt;figcaption&gt;I’ve generated these in 10 minutes, based on a screenshot of my banking app&lt;/figcaption&gt; &lt;/figure&gt;
&lt;p&gt;Look at the examples above. Which one do you pick, and why? Without knowing what works, you could go for any of them. Instead of designing, you’re shopping for options.&lt;/p&gt;
&lt;p&gt;Knowing why becomes important. “I just like this one” doesn’t really help. “This one, because the hierarchy is clearer thanks to the sensible use of white space” does, because someone else can understand it, challenge it and build on it. To me, taste is understanding why and being able to articulate it to others.&lt;sup&gt;[1]&lt;/sup&gt; &lt;/p&gt;
&lt;p&gt;By making things, you start to understand the material you’re working with, why you have to make certain choices, and why certain things don’t work. &lt;strong&gt;Making is thinking.&lt;/strong&gt; By letting a machine make for you instead, you run the risk of outsourcing your thinking AND your learning.&lt;/p&gt;
&lt;p&gt;I often see designers spending considerable time prompting for what doing it by hand would have shown them in a few minutes. It feels productive, but the real decisions get outsourced to more senior designers in review. These kinds of unread hand-offs are also referred to as slop grenades.&lt;sup&gt;[2]&lt;/sup&gt;  They cost the recipient a substantial amount of time to review, and over time they erode the abilities of the person who keeps throwing them.&lt;/p&gt;
&lt;div&gt; &lt;p&gt;I am not hating on AI&lt;/p&gt; &lt;div&gt; &lt;p&gt;I like using AI, it’s an enabler for me. A while ago, I built &lt;a href=&quot;https://robertpaauwe.com/blog/f-ck-paying-for-tools&quot;&gt;Omen&lt;/a&gt;, a vector illustration tool. The difference I care about is between using AI as a tool and letting it take the wheel, and that goes for me too.&lt;/p&gt; &lt;/div&gt; &lt;/div&gt;
&lt;h2 id=&quot;02-everything-is-going-to-look-the-same&quot;&gt;&lt;span&gt;02&lt;/span&gt; Everything is going to look the same&lt;/h2&gt;
&lt;p&gt;Effort used to be sort of a filter. Spending several weeks on a specific design usually meant you cared, because people don’t spend a lot of time on something they don’t care about.&lt;sup&gt;[3]&lt;/sup&gt; &lt;/p&gt;
&lt;p&gt;Now, it takes 10 minutes to prompt something and what you get is the average of everything the LLM has seen. You’ve probably seen these popping up everywhere. They’re today’s tells and will change, but the cause won’t:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Either a purple-blue gradient, or Anthropic beige;&lt;/li&gt;
&lt;li&gt;A lot of icons in circles;&lt;/li&gt;
&lt;li&gt;All-caps tags or pills sprinkled across the page;&lt;/li&gt;
&lt;li&gt;A dashboard with a stat banner showing metrics;&lt;/li&gt;
&lt;li&gt;Navbar items with emojis, or copy with excessive emojis;&lt;/li&gt;
&lt;li&gt;And many more examples.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;You can mask some of it with humanizer or design-taste skills. But if everybody does that, all work &lt;em&gt;still&lt;/em&gt; looks the same. Your competitor has access to the same LLMs, the same prompts and the same skills. So whatever you can do out of the box, your competitors can as well. When producing output is free, it is not something you can differentiate on anymore.&lt;sup&gt;[4]&lt;/sup&gt;  Output becomes the floor for everyone and that’s why ‘fine’ will be the new terrible.&lt;/p&gt;
&lt;div&gt; &lt;p&gt;Pushing back on my own argument&lt;/p&gt; &lt;div&gt; &lt;p&gt;For some work, fine is enough. Take a settings screen, a simple form to submit, usually very functional flows or features. People want to find the toggle and get out. A weird and unique settings screen is usually a worse one.&lt;/p&gt; &lt;/div&gt; &lt;/div&gt;
&lt;p&gt;Great pays off where the experience is the product. In the app I designed and built earlier this year, &lt;a href=&quot;https://robertpaauwe.com/projects/quiet-tarot&quot; title=&quot;Quiet Tarot&quot;&gt;Quiet Tarot&lt;/a&gt;, app store feedback directly reflects this. Most feedback praises the aesthetics and feeling of using the app, even though there are competitors who functionally do the same.&lt;/p&gt;
&lt;p&gt;A lot of that comes from small decisions. The app was designed first by hand, and then scaled later. The card interpretations are written around kitchen table reflections, instead of crystals, predictions and the universe. Reversed cards turn up less often, so your draws don’t feel like a confrontation.&lt;/p&gt;
&lt;p&gt;I gave Claude the same brief 3 times for a daily-card screen to illustrate what an uncurated version looks like. Style, layout and copy kept coming back across the iterations. It’s what you get when you converge to the average, if you don’t spend your time meticulously curating the output.&lt;/p&gt;
&lt;figure&gt; &lt;div&gt; &lt;div&gt; &lt;img src=&quot;https://robertpaauwe.com/_astro/fine-will-be-the-new-terrible-tarot-apps.D1v4X0uM_Z1qvsbz.webp&quot; srcset=&quot;https://robertpaauwe.com/_astro/fine-will-be-the-new-terrible-tarot-apps.D1v4X0uM_Z2nix3j.webp 400w, https://robertpaauwe.com/_astro/fine-will-be-the-new-terrible-tarot-apps.D1v4X0uM_Z2wfcTV.webp 600w, https://robertpaauwe.com/_astro/fine-will-be-the-new-terrible-tarot-apps.D1v4X0uM_Z1YaHI9.webp 900w, https://robertpaauwe.com/_astro/fine-will-be-the-new-terrible-tarot-apps.D1v4X0uM_Jtw8C.webp 1200w&quot; alt=&quot;A few daily-card screens that I made to illustrate slop.&quot; sizes=&quot;(min-width: 812px) 812px, 100vw&quot; width=&quot;2616&quot; height=&quot;1816&quot;&gt; &lt;/div&gt; &lt;/div&gt; &lt;figcaption&gt;A few daily-card screens that I made to illustrate slop.&lt;/figcaption&gt; &lt;/figure&gt;
&lt;p&gt;And to be fair, I didn’t get there with Quiet Tarot on my first try. Several card meanings weren’t perfect, because I settled for good enough. Until a 2-star review called the meanings too generic, and I ended up editing and rewriting 50 of the 78 cards.&lt;/p&gt;
&lt;h2 id=&quot;03-creating-the-conditions-for-making-good-work&quot;&gt;&lt;span&gt;03&lt;/span&gt; Creating the conditions for making good work&lt;/h2&gt;
&lt;p&gt;If everyone can produce output, quality has to be built into your system and workflows. This means that, rather than designing the output, designers are designing the conditions for good output to emerge. Your own context is the one input your competitor doesn’t have.&lt;/p&gt;
&lt;p&gt;This begins with writing down what the system should know. Not just the components and tokens, but why they exist and where the exceptions live. Usually, that stuff sits in people’s heads right now. If it isn’t explicit for your new joiners, it for sure isn’t explicit enough for any LLM.&lt;/p&gt;
&lt;p&gt;A system gets you consistency. To get beyond that, you have to know when to break it. A system is a record of decisions in the past, so following it keeps you consistent with the past, but it also restrains some of the design work.&lt;/p&gt;
&lt;p&gt;Recently, we redesigned the &lt;a href=&quot;https://www.iculture.nl/nieuws/rabobank-app-nieuw-design-personalisatie/&quot; title=&quot;Rabobank app&quot;&gt;Rabobank app&lt;/a&gt;. As part of that visual overhaul, we also built new page templates, so the app now supports a much more varied set of layouts. That gives teams more freedom, but using it well takes taste, skill and judgment, especially in knowing when a layout should break with what has been established before.&lt;/p&gt;
&lt;figure&gt; &lt;div&gt; &lt;div&gt; &lt;img src=&quot;https://robertpaauwe.com/_astro/reinterpretation-not-redesign-redesign-rabo-app.DMgZLNWE_ey3L9.webp&quot; srcset=&quot;https://robertpaauwe.com/_astro/reinterpretation-not-redesign-redesign-rabo-app.DMgZLNWE_kVxit.webp 400w, https://robertpaauwe.com/_astro/reinterpretation-not-redesign-redesign-rabo-app.DMgZLNWE_ZDliNT.webp 600w, https://robertpaauwe.com/_astro/reinterpretation-not-redesign-redesign-rabo-app.DMgZLNWE_Zf1cpX.webp 900w, https://robertpaauwe.com/_astro/reinterpretation-not-redesign-redesign-rabo-app.DMgZLNWE_ey3L9.webp 1180w&quot; alt=&quot;The redesigned Rabobank app&quot; sizes=&quot;(min-width: 588px) 588px, 100vw&quot; width=&quot;1180&quot; height=&quot;1157&quot;&gt; &lt;/div&gt; &lt;/div&gt;  &lt;/figure&gt;
&lt;h2 id=&quot;04-building-taste-on-purpose&quot;&gt;&lt;span&gt;04&lt;/span&gt; Building taste on purpose&lt;/h2&gt;
&lt;p&gt;Taste used to be a side effect of making things: you kept going past the first version that worked. If making things goes away, then how do you acquire taste? It has to be practiced on purpose. A common complaint is that this lack of craft keeps juniors from growing into seniors. One way to counter that is to actively train teams in routines that build taste and craft:&lt;/p&gt;
&lt;div&gt; &lt;div&gt; &lt;div&gt; 1 &lt;/div&gt; &lt;div&gt; &lt;p&gt;Old school critique, but it’s AI&lt;/p&gt; &lt;p&gt;Give your team a set of AI-generated options for a real problem. Everyone writes down what works and what doesn’t for each option, like an old-school design critique. For a second round, ask an AI model to critique the same options and judge that critique together: which points are fair, which are generic, and which miss the point?&lt;/p&gt; &lt;/div&gt; &lt;/div&gt;&lt;div&gt; &lt;div&gt; 2 &lt;/div&gt; &lt;div&gt; &lt;p&gt;Back to pen and paper&lt;/p&gt; &lt;p&gt;Have your team work on a real design problem on paper. Only use fat, thick markers so nobody can draw any details. Forcing yourself to express in the broadest rough details possible forces you to think of the essence of what you’re doing.&lt;/p&gt; &lt;/div&gt; &lt;/div&gt;&lt;div&gt; &lt;div&gt; 3 &lt;/div&gt; &lt;div&gt; &lt;p&gt;The 5-whys&lt;/p&gt; &lt;p&gt;An idea taken from my engineering background. This is a method for root cause analysis. Take anyone’s design, and keep asking why (usually it’s 5 times) about a certain design decision until you fundamentally understand why it is the way it is. Keep digging until you can’t go any deeper.&lt;/p&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt;
&lt;p&gt;None of these sound particularly exciting, but that’s how craftsmanship is built. Through routine, through repetition, and through discipline. You have to continuously maintain your own set of knowledge and deep understanding of why something is good or bad.&lt;/p&gt;
&lt;figure&gt; &lt;div&gt; &lt;div&gt; &lt;img src=&quot;https://robertpaauwe.com/_astro/fine-will-be-the-new-terrible-pages-sketch.BzSM0VCp_1b00Pz.webp&quot; srcset=&quot;https://robertpaauwe.com/_astro/fine-will-be-the-new-terrible-pages-sketch.BzSM0VCp_ZAOd0c.webp 400w, https://robertpaauwe.com/_astro/fine-will-be-the-new-terrible-pages-sketch.BzSM0VCp_1FNqR5.webp 600w, https://robertpaauwe.com/_astro/fine-will-be-the-new-terrible-pages-sketch.BzSM0VCp_ZBppdR.webp 900w, https://robertpaauwe.com/_astro/fine-will-be-the-new-terrible-pages-sketch.BzSM0VCp_Z2k9qgp.webp 1200w&quot; alt=&quot;Original sketch I did of our full-page template, done with pen and paper&quot; sizes=&quot;(min-width: 588px) 588px, 100vw&quot; width=&quot;1422&quot; height=&quot;1702&quot;&gt; &lt;/div&gt; &lt;/div&gt; &lt;figcaption&gt;Original sketch I did of our full-page template, done with pen and paper&lt;/figcaption&gt; &lt;/figure&gt;
&lt;h2 id=&quot;05-separating-fine-from-great&quot;&gt;&lt;span&gt;05&lt;/span&gt; Separating ‘fine’ from great&lt;/h2&gt;
&lt;p&gt;In the end, I welcome more people making things. But being able to produce output doesn’t excuse you from thinking and understanding.&lt;/p&gt;
&lt;p&gt;I think that’s what goes wrong with the prototype example in the opening. People confuse producing output with deep thinking about it. As if generating the output is the same as a designer deeply thinking about all the different considerations. &lt;sup&gt;[5]&lt;/sup&gt; &lt;/p&gt;
&lt;p&gt;So what is the point of a designer? Treat your designers as your conscience. They know which decisions are load-bearing, where the system should bend, and why. Let them help you decide where fine is enough and where the experience is the product, and spend their time on the latter.&lt;/p&gt;
&lt;p&gt;And if you’re the one handing work over: review what you made &lt;strong&gt;before&lt;/strong&gt; you hand it to someone else. When a slop grenade lands in your lap, don’t just review the work. Ask:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;What was your prompt?&lt;/li&gt;
&lt;li&gt;What problem does this solve?&lt;/li&gt;
&lt;li&gt;Where does it break the design system?&lt;/li&gt;
&lt;li&gt;What other options have you explored?&lt;/li&gt;
&lt;li&gt;Why did you land on this version?&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;If the one sending the grenade can’t answer any of these, then I think that says enough.&lt;/p&gt;&lt;hr&gt;&lt;ol&gt;&lt;li&gt;I turned to Rick Rubin’s The Creative Act hoping to understand taste better. There are a few nuggets of wisdom: “Look for what you notice but no one else sees.” It’s the opposite of what an LLM does, which gives you the average of everything. Sadly, the book rarely explains the why behind its wisdom or digs any deeper into how to operationalize things. &lt;a href=&quot;https://doublechorus.substack.com/p/048-i-hated-rick-rubins-book-but&quot; target=&quot;_blank&quot; rel=&quot;noopener noreferrer&quot;&gt;
Source
&lt;/a&gt;&lt;/li&gt;&lt;li&gt;AI output passed to a colleague without being read or checked, so the colleague does the checking. It can apply to design, writing, code or any other AI output. &lt;a href=&quot;https://www.businessinsider.com/shopify-ceo-ai-slop-grenades-can-make-work-harder-2026-9&quot; target=&quot;_blank&quot; rel=&quot;noopener noreferrer&quot;&gt;
Source
&lt;/a&gt;&lt;/li&gt;&lt;li&gt;Do note that effort doesn’t necessarily mean the work is good.&lt;/li&gt;&lt;li&gt;Not literally free. Among the businesses Ramp tracks, token spend grew 497% between January 2025 and April 2026. But for the person typing the prompt it feels free, especially in a large organization where someone else is paying the bill. &lt;a href=&quot;https://ramp.com/blog/ai-token-cost-for-businesses&quot; target=&quot;_blank&quot; rel=&quot;noopener noreferrer&quot;&gt;
Source
&lt;/a&gt;&lt;/li&gt;&lt;li&gt;Daniel Miessler described it well in his recent blog. Vibe-coding isn’t the same as using AI to make things. Producing output isn’t the same as understanding what you’re doing anymore. &lt;a href=&quot;https://danielmiessler.com/blog/vibe-coding-isnt-using-ai&quot; target=&quot;_blank&quot; rel=&quot;noopener noreferrer&quot;&gt;
Source
&lt;/a&gt;&lt;/li&gt;&lt;/ol&gt;</content>
  </entry>
  <entry>
    <title>Some thoughts on reinterpretation and redesign (and death metal)</title>
    <link href="https://robertpaauwe.com/blog/reinterpretation-and-redesign/" rel="alternate" type="text/html" />
    <id>https://robertpaauwe.com/blog/reinterpretation-and-redesign/</id>
    <published>2026-09-26T00:00:00.000Z</published>
    <updated>2026-09-28T00:00:00.000Z</updated>
    <summary>How death metal, van Gogh, and Orthodox iconography are related to redesigning banking apps.</summary>
    <category term="design" />
    <category term="craft" />
    <category term="redesign" />
    <content type="html">&lt;p&gt;Earlier this year, one of my favorite albums got a rerelease. Opeth’s &lt;em&gt;Blackwater Park,&lt;/em&gt; in my opinion, is one of the best albums ever created. &lt;sup&gt;[1]&lt;/sup&gt;  For progressive death metal, it’s moody, it’s bleak, it’s spacious and ethereal. It’s why I was surprised the rerelease in 2026 received a new album design. For me, the original really captured the feeling and mood of the album. Icy, bleak, misty, unresolved.&lt;/p&gt;
&lt;p&gt;The new album cover has the same subject; a swampy wood with twisted trees and unrecognizable figures in the distance.&lt;/p&gt;
&lt;p&gt;The new album is much darker and creepy. Now I am all for &lt;a href=&quot;https://robertpaauwe.com/illustrations&quot;&gt;dark and creepy&lt;/a&gt;, but the ‘reinterpretation’ didn’t feel right for me. Maybe it’s nostalgia, but the new visuals do not match the album for me.&lt;/p&gt;
&lt;div&gt; &lt;figure&gt; &lt;img src=&quot;https://robertpaauwe.com/_astro/reinterpretation-not-redesign-redesign-blackwaterpark-original.DdzhQJck_yg4iO.webp&quot; alt=&quot;Original 2001 Blackwater Park album cover&quot; width=&quot;1000&quot; height=&quot;1000&quot;&gt; &lt;figcaption&gt;Original 2001 Blackwater Park album cover&lt;/figcaption&gt; &lt;/figure&gt; &lt;figure&gt; &lt;img src=&quot;https://robertpaauwe.com/_astro/reinterpretation-not-redesign-redesign-blackwaterpark-rerelease.C3xMmomX_s2KwO.webp&quot; alt=&quot;2026 rerelease album cover&quot; width=&quot;1000&quot; height=&quot;1000&quot;&gt; &lt;figcaption&gt;2026 rerelease album cover&lt;/figcaption&gt; &lt;/figure&gt; &lt;/div&gt;
&lt;h2 id=&quot;01-perfection-of-the-same-idea&quot;&gt;&lt;span&gt;01&lt;/span&gt; Perfection of the same idea&lt;/h2&gt;
&lt;p&gt;Reinterpretation happens a lot in art. Van Gogh painted the same sunflowers seven times between August 1888 and January 1889. Some of those were near-identical copies made for family, but in others he used the same subject as an excuse to try new color combinations each time. &lt;sup&gt;[2]&lt;/sup&gt; &lt;/p&gt;
&lt;div&gt; &lt;figure&gt; &lt;img src=&quot;https://robertpaauwe.com/_astro/reinterpretation-not-redesign-redesign-vangogh-original.DRHLAY_a_3YQTP.webp&quot; alt=&quot;Still Life: Vase with Twelve Sunflowers (1888)&quot; width=&quot;1000&quot; height=&quot;1250&quot;&gt; &lt;figcaption&gt;Still Life: Vase with Twelve Sunflowers (1888)&lt;/figcaption&gt; &lt;/figure&gt; &lt;figure&gt; &lt;img src=&quot;https://robertpaauwe.com/_astro/reinterpretation-not-redesign-redesign-vangogh-repetition.KUge9L8e_Z2sm5Y6.webp&quot; alt=&quot;Still Life: Vase with Twelve Sunflowers (1889), repetition&quot; width=&quot;1000&quot; height=&quot;1250&quot;&gt; &lt;figcaption&gt;Still Life: Vase with Twelve Sunflowers (1889), repetition&lt;/figcaption&gt; &lt;/figure&gt; &lt;/div&gt;
&lt;p&gt;Matisse did two versions of the same still life a year apart, &lt;em&gt;Still Life with Purro I&lt;/em&gt; and &lt;em&gt;II&lt;/em&gt;, identical composition, and you can watch him change style from solid thick brushwork into pointillism.&lt;/p&gt;
&lt;div&gt; &lt;figure&gt; &lt;img src=&quot;https://robertpaauwe.com/_astro/reinterpretation-not-redesign-redesign-still-life-with-purro1.B4Jp9hOC_Zwf4Oj.webp&quot; alt=&quot;Still life with purro I (1904)&quot; width=&quot;1000&quot; height=&quot;821&quot;&gt; &lt;figcaption&gt;Still life with purro I (1904)&lt;/figcaption&gt; &lt;/figure&gt; &lt;figure&gt; &lt;img src=&quot;https://robertpaauwe.com/_astro/reinterpretation-not-redesign-redesign-still-life-with-purro2.CeOvRfjv_Zt6Gy0.webp&quot; alt=&quot;Still life with purro II (1904-1905)&quot; width=&quot;1000&quot; height=&quot;821&quot;&gt; &lt;figcaption&gt;Still life with purro II (1904-1905)&lt;/figcaption&gt; &lt;/figure&gt; &lt;/div&gt;
&lt;p&gt;Leonardo painted &lt;em&gt;Virgin of the Rocks&lt;/em&gt; twice, twenty years apart, though not by choice. The first version got tangled in a payment dispute with the confraternity that commissioned it, and the second exists because the argument dragged on for two decades before he agreed to finish it.&lt;/p&gt;
&lt;div&gt; &lt;figure&gt; &lt;img src=&quot;https://robertpaauwe.com/_astro/reinterpretation-not-redesign-redesign-virgin-of-the-rocks-1486.DJ-DM9pw_Z1yjdAO.webp&quot; alt=&quot;First version of Virgin of the Rocks (1483-1486)&quot; width=&quot;960&quot; height=&quot;1522&quot;&gt; &lt;figcaption&gt;The Paris version Virgin of the Rocks (1483-1486)&lt;/figcaption&gt; &lt;/figure&gt; &lt;figure&gt; &lt;img src=&quot;https://robertpaauwe.com/_astro/reinterpretation-not-redesign-redesign-virgin-of-the-rocks-1508.8mC5bn8X_1iNSQh.webp&quot; alt=&quot;The London version of Virgin of the Rocks (1495-1508)&quot; width=&quot;960&quot; height=&quot;1522&quot;&gt; &lt;figcaption&gt;The London version of Virgin of the Rocks (1495-1508)&lt;/figcaption&gt; &lt;/figure&gt; &lt;/div&gt;
&lt;p&gt;An even more extreme version of this exists within Orthodox icon painting. It’s been described as a conservative craft in which the painter is essentially a tool for replication. What matters most is fidelity to the image that came before. Generation after generation, the same composition redrawn by different hands across centuries.&lt;/p&gt;
&lt;figure&gt; &lt;div&gt; &lt;div&gt; &lt;img src=&quot;https://robertpaauwe.com/_astro/reinterpretation-not-redesign-redesign-theotokos.Ve696Xpq_1tcLRI.webp&quot; srcset=&quot;https://robertpaauwe.com/_astro/reinterpretation-not-redesign-redesign-theotokos.Ve696Xpq_16yu1i.webp 400w, https://robertpaauwe.com/_astro/reinterpretation-not-redesign-redesign-theotokos.Ve696Xpq_1TPnBj.webp 600w, https://robertpaauwe.com/_astro/reinterpretation-not-redesign-redesign-theotokos.Ve696Xpq_1f6vMY.webp 900w, https://robertpaauwe.com/_astro/reinterpretation-not-redesign-redesign-theotokos.Ve696Xpq_Z1iLzJf.webp 1200w&quot; alt=&quot;Left: Theotokos of Vladimir (1125), Right: Theotokos of the Don (1382-1395)&quot; sizes=&quot;(min-width: 588px) 588px, 100vw&quot; width=&quot;2000&quot; height=&quot;1417&quot;&gt; &lt;/div&gt; &lt;/div&gt; &lt;figcaption&gt;Left: Theotokos of Vladimir (1125), Right: Theotokos of the Don (1382-1395)&lt;/figcaption&gt; &lt;/figure&gt;
&lt;p&gt;There is no merit in inventing a new Christ or a new Theotokos. Faithful repetition, created by someone with a steadier hand than the last person, is the holy grail. &lt;sup&gt;[3]&lt;/sup&gt; &lt;/p&gt;
&lt;h2 id=&quot;02-redesign-and-reinterpretation-have-different-goals&quot;&gt;&lt;span&gt;02&lt;/span&gt; Redesign and reinterpretation have different goals&lt;/h2&gt;
&lt;p&gt;When something gets redesigned, for example a banking app, the old version doesn’t get to stick around as a valid alternative. Nobody gets to keep the old app installed next to the new one out of preference. This is why redesigns are always complex to roll out: people &lt;strong&gt;hate&lt;/strong&gt; change.&lt;sup&gt;[4]&lt;/sup&gt; &lt;/p&gt;
&lt;p&gt;This summer, we &lt;a href=&quot;https://www.iculture.nl/nieuws/rabobank-app-nieuw-design-personalisatie/&quot;&gt;redesigned the Rabo App&lt;/a&gt;. A redesign at this scale takes a tremendous effort by a large group of people; designers, creative direction, engineers, product managers, marketing, and many others all working towards the same thing: the new replacing the old.&lt;/p&gt;
&lt;figure&gt; &lt;div&gt; &lt;div&gt; &lt;img src=&quot;https://robertpaauwe.com/_astro/reinterpretation-not-redesign-redesign-rabo-app.DMgZLNWE_ey3L9.webp&quot; srcset=&quot;https://robertpaauwe.com/_astro/reinterpretation-not-redesign-redesign-rabo-app.DMgZLNWE_kVxit.webp 400w, https://robertpaauwe.com/_astro/reinterpretation-not-redesign-redesign-rabo-app.DMgZLNWE_ZDliNT.webp 600w, https://robertpaauwe.com/_astro/reinterpretation-not-redesign-redesign-rabo-app.DMgZLNWE_Zf1cpX.webp 900w, https://robertpaauwe.com/_astro/reinterpretation-not-redesign-redesign-rabo-app.DMgZLNWE_ey3L9.webp 1180w&quot; alt=&quot;Left: old design of the Rabo App, Right: The 2026 redesign&quot; sizes=&quot;(min-width: 812px) 812px, 100vw&quot; width=&quot;1180&quot; height=&quot;1157&quot;&gt; &lt;/div&gt; &lt;/div&gt; &lt;figcaption&gt;Left: old design of the Rabo App, Right: The 2026 redesign&lt;/figcaption&gt; &lt;/figure&gt;
&lt;p&gt;It’s the right call here: the app serves millions of people daily, and it has to evolve with their needs, the bank’s systems, and the times. That’s where redesign is different from reinterpretation.&lt;/p&gt;
&lt;p&gt;The old version is finished, closed, over, done. That doesn’t mean the old was bad. It was very good at the time it was released. But context changes, and sometimes redesigns are needed to stay up to date, set the stage for upcoming things, evolve with the brand, or improve things under the hood.&lt;sup&gt;[5]&lt;/sup&gt; &lt;/p&gt;
&lt;h2 id=&quot;03-some-ideas-need-time&quot;&gt;&lt;span&gt;03&lt;/span&gt; Some ideas need time&lt;/h2&gt;
&lt;p&gt;A reinterpretation is different. Sometimes the idea needs time to catch up with the person. Maybe the concept was really good, the execution just wasn’t there yet. Maybe you want several versions to give to your family, like van Gogh. Maybe the original idea needs refining for it to become &lt;em&gt;really&lt;/em&gt; good.&lt;/p&gt;
&lt;figure&gt; &lt;blockquote&gt; &lt;p&gt;Sometimes, a good idea needs to wait for a future version of you to become incredible.&lt;/p&gt; &lt;/blockquote&gt;  &lt;/figure&gt;
&lt;p&gt;To go back and iterate on an old idea is not a bad thing. You have greater skill, new context, and a fresh perspective. What matters is what happens to the original once the new version exists.&lt;/p&gt;
&lt;p&gt;Reinterpretation, done right, doesn’t replace the old version. It just adds another version to stand next to it. The old one is still allowed to be the version some people prefer, still allowed to be correct on its own terms.&lt;/p&gt;
&lt;aside&gt; &lt;p&gt;&lt;strong&gt;Notable exceptions&lt;/strong&gt;&lt;/p&gt; &lt;div&gt; &lt;p&gt;There are some notable exceptions to this; I prefer the theatrical cut of the original 1977-1983 Star Wars trilogy. I don’t mind the changes George Lucas made to later reissues, but he also actively suppressed the original versions. Same for album remasters that replaced the old (e.g., the 2009 Beatles remasters on streaming services). Suddenly a reissue becomes the only version of the release available.&lt;/p&gt; &lt;/div&gt; &lt;/aside&gt;
&lt;h2 id=&quot;04-where-that-leaves-me&quot;&gt;&lt;span&gt;04&lt;/span&gt; Where that leaves me&lt;/h2&gt;
&lt;p&gt;My feelings for the &lt;em&gt;Blackwater Park&lt;/em&gt; reissue resolve in accepting this as a reinterpretation. The cover is fine. Currently, both album covers are still available side-by-side.&lt;sup&gt;[6]&lt;/sup&gt;  But time will tell if the reissue starts taking over its position as &lt;em&gt;the&lt;/em&gt; cover, if the old will be replaced and archived. &lt;em&gt;Then&lt;/em&gt; it becomes a redesign instead of a reinterpretation.&lt;/p&gt;
&lt;p&gt;I would &lt;strong&gt;hate&lt;/strong&gt; that.&lt;/p&gt;
&lt;p&gt;I reinterpret my own work as well. Back in 2018-2019 my illustrations weren’t particularly good, but I like those original ideas. Going back to one of those pieces now isn’t correcting a mistake I made back then. For me, it’s having a second attempt at the same idea.&lt;/p&gt;
&lt;div&gt; &lt;figure&gt; &lt;img src=&quot;https://robertpaauwe.com/_astro/reinterpretation-not-redesign-redesign-goat-2019.CI0U5_dZ_Z2l7LXg.webp&quot; alt=&quot;Habergeiß, Robert A. Paauwe (2019)&quot; width=&quot;1000&quot; height=&quot;1250&quot;&gt; &lt;figcaption&gt;Habergeiß, Robert A. Paauwe (2019)&lt;/figcaption&gt; &lt;/figure&gt; &lt;figure&gt; &lt;img src=&quot;https://robertpaauwe.com/_astro/reinterpretation-not-redesign-redesign-goat-2019-2.yX64YIZz_1lso6h.webp&quot; alt=&quot;Habergeiß, Robert A. Paauwe (2025)&quot; width=&quot;1000&quot; height=&quot;1250&quot;&gt; &lt;figcaption&gt;Habergeiß, Robert A. Paauwe (2025)&lt;/figcaption&gt; &lt;/figure&gt; &lt;/div&gt;
&lt;p&gt;What changed is me. I learned new techniques, found better ways of doing things, and developed a better sense of taste. I am giving old ideas a new interpretation with all the things I learned along the way.&lt;/p&gt;
&lt;p&gt;So go back. Find old sketches, drafts, or ideas you’ve shelved because you weren’t good enough for them yet.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;You might be now.&lt;/em&gt;&lt;/p&gt;&lt;hr&gt;&lt;ol&gt;&lt;li&gt;You should really listen to it, even if you’re not into death metal. &lt;a href=&quot;https://open.spotify.com/track/4xQl7d1pI8kbT0vb7cdnjC?si=aab14a4489b54f20&quot; target=&quot;_blank&quot; rel=&quot;noopener noreferrer&quot;&gt;
Source
&lt;/a&gt;&lt;/li&gt;&lt;li&gt;I am not an art historian so the interpretation of these works is probably a lot more nuanced than my limited ability allows.&lt;/li&gt;&lt;li&gt;The Acts of the Second Council of Nicaea are often quoted as saying that icon-making follows the tradition handed down by the Fathers rather than the invention of the individual painter.&lt;/li&gt;&lt;li&gt;Nielsen Norman Group’s advice to design teams is blunt about it: users hate change, full stop, regardless of whether the new design is actually better. &lt;a href=&quot;https://www.nngroup.com/videos/users-hate-change/&quot; target=&quot;_blank&quot; rel=&quot;noopener noreferrer&quot;&gt;
Source
&lt;/a&gt;&lt;/li&gt;&lt;li&gt;There are many other reasons to do a redesign.  &lt;a href=&quot;https://www.prismetric.com/unlock-opportunities-mobile-app-redesigning/&quot; target=&quot;_blank&quot; rel=&quot;noopener noreferrer&quot;&gt;
Source
&lt;/a&gt;&lt;/li&gt;&lt;li&gt;One of my favorite reinterpretations is Cradle of Filth’s 2019 version of &lt;em&gt;Cruelty and the Beast&lt;/em&gt;. The 1998 version is a masterpiece, but riddled with poor mixing and recording. The 2019 version largely solves that: it is incredible. I do enjoy the 1998 version too, for its raw and more visceral nature. &lt;a href=&quot;https://open.spotify.com/album/1b7Yy5kprvU3YiJmRdt4Bf?si=J8GQSV0ZRKmkadiWwUAl4w&quot; target=&quot;_blank&quot; rel=&quot;noopener noreferrer&quot;&gt;
Source
&lt;/a&gt;&lt;/li&gt;&lt;/ol&gt;</content>
  </entry>
  <entry>
    <title>F*ck paying for tools, I'll build my own</title>
    <link href="https://robertpaauwe.com/blog/f-ck-paying-for-tools/" rel="alternate" type="text/html" />
    <id>https://robertpaauwe.com/blog/f-ck-paying-for-tools/</id>
    <published>2026-09-05T00:00:00.000Z</published>
    <updated>2026-09-05T00:00:00.000Z</updated>
    <summary>Everything becomes worse and more expensive. Why not make something better myself?</summary>
    <category term="making" />
    <category term="tools" />
    <content type="html">&lt;p&gt;The past year or so I have lost the joy of illustration. For most of my &lt;a href=&quot;https://robertpaauwe.com/illustrations&quot;&gt;illustrations&lt;/a&gt;, I used to use Adobe Illustrator. It’s a great tool, but as a hobbyist, the cost of it started to outweigh the benefits.&lt;/p&gt;
&lt;p&gt;The single-app plan runs close to 40 euros a month if you want the freedom to cancel whenever. That’s close to 500 euros. Pay a year up front, and you’ll still spend over 300 euros per year.&lt;/p&gt;
&lt;h2 id=&quot;01-other-tools-are-kinda-shit&quot;&gt;&lt;span&gt;01&lt;/span&gt; Other tools are kinda shit&lt;/h2&gt;
&lt;p&gt;Maybe an exaggeration. &lt;a href=&quot;https://inkscape.org/&quot; target=&quot;_blank&quot;&gt;Inkscape&lt;/a&gt; is actually kinda good, and it’s free. I use it a lot for my pen plotter, Axidraw &lt;sup&gt;[1]&lt;/sup&gt;  has an amazing plugin for it. But Inkscape has some very odd choices baked into the UI and always messes up my way of working. Most of my illustration work is built on repeating patterns, and I’ve built a workaround in Adobe Illustrator for it. That didn’t really translate well to Inkscape and those patterns slowed the application down to nearly unusable.&lt;/p&gt;
&lt;p&gt;I’ve also tried &lt;a href=&quot;https://affinity.serif.com/&quot; target=&quot;_blank&quot;&gt;Affinity&lt;/a&gt;. It’s not bad at all. It’s currently free and has several useful features. But I fear it won’t be free forever and then I’d be stuck with another workflow that I eventually have to unlearn. Also the pattern tool in Affinity didn’t work. It just didn’t work at all.&lt;/p&gt;
&lt;figure&gt; &lt;div&gt; &lt;div&gt; &lt;img src=&quot;https://robertpaauwe.com/_astro/cup_curse-exe_pattern.CqwwrIUO_Z2pH8JU.webp&quot; srcset=&quot;https://robertpaauwe.com/_astro/cup_curse-exe_pattern.CqwwrIUO_ZWHTIg.webp 400w, https://robertpaauwe.com/_astro/cup_curse-exe_pattern.CqwwrIUO_Z2r0N2L.webp 600w, https://robertpaauwe.com/_astro/cup_curse-exe_pattern.CqwwrIUO_Z2tCRm5.webp 900w, https://robertpaauwe.com/_astro/cup_curse-exe_pattern.CqwwrIUO_Z2pH8JU.webp 1080w&quot; alt=&quot;Left: pattern on the left does not load in Affinity. Right: original illustration.&quot; sizes=&quot;(min-width: 588px) 588px, 100vw&quot; width=&quot;1080&quot; height=&quot;1350&quot;&gt; &lt;/div&gt; &lt;/div&gt; &lt;figcaption&gt;Left: pattern on the left does not load in Affinity. Right: original illustration.&lt;/figcaption&gt; &lt;/figure&gt;
&lt;p&gt;I realized using shitty tools took the fun out of illustration for me. I spend most of my time figuring out how to do the same thing that I already knew how to.&lt;/p&gt;
&lt;h2 id=&quot;02-how-hard-can-it-be&quot;&gt;&lt;span&gt;02&lt;/span&gt; How hard can it be?&lt;/h2&gt;
&lt;p&gt;Building &lt;a href=&quot;https://robertpaauwe.com/projects/quiet-tarot&quot;&gt;Quiet Tarot&lt;/a&gt; earlier this year changed how I look at design and design tools. With Claude and other code assistants, I can not only build a solution, but quickly create a tool to solve my specific problem.&lt;/p&gt;
&lt;figure&gt; &lt;div&gt; &lt;div&gt; &lt;img src=&quot;https://robertpaauwe.com/_astro/copy-tool_quiet-tarot.Ed7KY6oO_2hblIo.webp&quot; srcset=&quot;https://robertpaauwe.com/_astro/copy-tool_quiet-tarot.Ed7KY6oO_1SzTAN.webp 400w, https://robertpaauwe.com/_astro/copy-tool_quiet-tarot.Ed7KY6oO_Z1jFmRP.webp 600w, https://robertpaauwe.com/_astro/copy-tool_quiet-tarot.Ed7KY6oO_2hblIo.webp 900w&quot; alt=&quot;Copy tool that I've built for Quiet Tarot&quot; sizes=&quot;(min-width: 812px) 812px, 100vw&quot; width=&quot;900&quot; height=&quot;588&quot;&gt; &lt;/div&gt; &lt;/div&gt; &lt;figcaption&gt;Copy tool that I&amp;#39;ve built for Quiet Tarot&lt;/figcaption&gt; &lt;/figure&gt;
&lt;p&gt;For Quiet Tarot, I built several tools to make my life easier. One to manage copy &lt;sup&gt;[2]&lt;/sup&gt;  at scale, and one to track my product testing. These tools were simple JSON editors, so building my own SVG / vector tools was a bit of a stretch.&lt;/p&gt;
&lt;p&gt;So I went in with a pretty yolo mindset: just start and see where it takes me. Claude advised against it, for it being highly complex and unrealistic to build. I’ve made a quick UI sketch in TLDraw &lt;sup&gt;[3]&lt;/sup&gt;  and wrote a quick &lt;a href=&quot;https://en.wikipedia.org/wiki/Product_requirements_document&quot; target=&quot;_blank&quot;&gt;PRD&lt;/a&gt;. I based the requirements on specifically the tools I use in my workflow and descoped all the rest.&lt;/p&gt;
&lt;figure&gt; &lt;div&gt; &lt;div&gt; &lt;img src=&quot;https://robertpaauwe.com/_astro/tldraw_omen.CfmVrdoE_fAwOo.webp&quot; srcset=&quot;https://robertpaauwe.com/_astro/tldraw_omen.CfmVrdoE_2kNW8G.webp 400w, https://robertpaauwe.com/_astro/tldraw_omen.CfmVrdoE_2sPG9l.webp 600w, https://robertpaauwe.com/_astro/tldraw_omen.CfmVrdoE_Z21LxNh.webp 900w, https://robertpaauwe.com/_astro/tldraw_omen.CfmVrdoE_3Xra4.webp 1200w&quot; alt=&quot;First sketch of the app as input for Claude&quot; sizes=&quot;(min-width: 812px) 812px, 100vw&quot; width=&quot;2452&quot; height=&quot;1515&quot;&gt; &lt;/div&gt; &lt;/div&gt; &lt;figcaption&gt;First sketch of the app as input for Claude&lt;/figcaption&gt; &lt;/figure&gt;
&lt;h2 id=&quot;03-done-and-feature-complete-in-one-week&quot;&gt;&lt;span&gt;03&lt;/span&gt; Done and feature-complete in one week&lt;/h2&gt;
&lt;p&gt;I broke the PRD up into 25 phases, each building on top of the previous phase. Each phase came with its own design brief and scope. I’ve learned that scoping in Claude is amazing. Tight design briefs for each phase allowed me to build each step quite quickly as it built upon each previous step.&lt;/p&gt;
&lt;figure&gt; &lt;div&gt; &lt;div&gt; &lt;img src=&quot;https://robertpaauwe.com/_astro/phases_omen.Cv6CmFme_Z2dkn3v.webp&quot; srcset=&quot;https://robertpaauwe.com/_astro/phases_omen.Cv6CmFme_ZlOe8f.webp 400w, https://robertpaauwe.com/_astro/phases_omen.Cv6CmFme_Z2dkn3v.webp 481w&quot; alt=&quot;Phases of the app as input for Claude&quot; sizes=&quot;(min-width: 588px) 588px, 100vw&quot; width=&quot;481&quot; height=&quot;943&quot;&gt; &lt;/div&gt; &lt;/div&gt; &lt;figcaption&gt;Phases of the app as input for Claude&lt;/figcaption&gt; &lt;/figure&gt;
&lt;p&gt;The first 7 phases were really just getting a working MVP: canvas and pan/zoom, the pencil tool, pattern fills with global registration so hatching lines up across separate shapes, undo/redo, and save-straight-to-disk.&lt;/p&gt;
&lt;p&gt;Everything after that was refinement. A chunk of phases went into the basics: export, layers, guides and snapping, selection tools, arrange tools, etc. Another chunk went into improving stability and making life easier. Most of the initial phases went quite fast. I did a minor iteration in TLDraw to cobble some screenshots together to sketch what I wanted.&lt;/p&gt;
&lt;figure&gt; &lt;div&gt; &lt;div&gt; &lt;img src=&quot;https://robertpaauwe.com/_astro/omen_iteration.CT-KFv02_mmDQS.webp&quot; srcset=&quot;https://robertpaauwe.com/_astro/omen_iteration.CT-KFv02_1emYfT.webp 400w, https://robertpaauwe.com/_astro/omen_iteration.CT-KFv02_1bteMI.webp 600w, https://robertpaauwe.com/_astro/omen_iteration.CT-KFv02_ZCliuS.webp 900w, https://robertpaauwe.com/_astro/omen_iteration.CT-KFv02_Z1PGuJW.webp 1200w&quot; alt=&quot;Iteration of the app as input for Claude&quot; sizes=&quot;(min-width: 812px) 812px, 100vw&quot; width=&quot;2000&quot; height=&quot;1009&quot;&gt; &lt;/div&gt; &lt;/div&gt; &lt;figcaption&gt;Iteration of the app as input for Claude&lt;/figcaption&gt; &lt;/figure&gt;
&lt;p&gt;The original scope expanded from 16 to 25 phases, as a few features turned out to be quite useful in my workflow (and it was quite easy to build). Multi-artboard support, templates, type support, even a Live Trace tool to auto-vectorize a scanned sketch into editable paths. I also decided to wrap the whole thing into a standalone desktop app, so I don’t need a browser tab open just to draw.&lt;/p&gt;
&lt;p&gt;I built it almost entirely in Claude Code in the evening hours over the course of a week using mostly Sonnet with a bit of Opus mixed in, on a Pro subscription. The biggest bottleneck was working around the daily limit.&lt;/p&gt;
&lt;figure&gt; &lt;div&gt; &lt;div&gt; &lt;img src=&quot;https://robertpaauwe.com/_astro/omen_full-app.Ct6F64Tg_oPWxQ.webp&quot; srcset=&quot;https://robertpaauwe.com/_astro/omen_full-app.Ct6F64Tg_Z2qcFSI.webp 400w, https://robertpaauwe.com/_astro/omen_full-app.Ct6F64Tg_Z1kGINs.webp 600w, https://robertpaauwe.com/_astro/omen_full-app.Ct6F64Tg_ZQKpOj.webp 900w, https://robertpaauwe.com/_astro/omen_full-app.Ct6F64Tg_Z2tYNnw.webp 1200w&quot; alt=&quot;Full app&quot; sizes=&quot;(min-width: 812px) 812px, 100vw&quot; width=&quot;2000&quot; height=&quot;1089&quot;&gt; &lt;/div&gt; &lt;/div&gt; &lt;figcaption&gt;Full app&lt;/figcaption&gt; &lt;/figure&gt;
&lt;h2 id=&quot;04-pattern-control-and-exporting-videos-turn-out-to-be-sick&quot;&gt;&lt;span&gt;04&lt;/span&gt; Pattern control and exporting videos turn out to be sick&lt;/h2&gt;
&lt;p&gt;The app, which I’ve named Omen, is actually &lt;em&gt;really&lt;/em&gt; good. In particular, the pattern tool is exactly what I wanted, and I haven’t seen any other app that comes even close. The pattern tool is fast and high-performance. Where Inkscape and Affinity choked on patterns, Omen handles them with ease. Additionally, you can control the pattern set to make sure the cross hatches always match as you adjust size, roughness and randomness.&lt;/p&gt;
&lt;figure&gt; &lt;div&gt; &lt;div&gt; &lt;img src=&quot;https://robertpaauwe.com/_astro/omen_pattern.BsGBxl44_ZjP3hr.webp&quot; srcset=&quot;https://robertpaauwe.com/_astro/omen_pattern.BsGBxl44_Z1b263B.webp 400w, https://robertpaauwe.com/_astro/omen_pattern.BsGBxl44_ZHef9q.webp 600w, https://robertpaauwe.com/_astro/omen_pattern.BsGBxl44_Z1sdfwG.webp 900w, https://robertpaauwe.com/_astro/omen_pattern.BsGBxl44_Zsozxv.webp 1200w&quot; alt=&quot;My pattern tool allows a lot of tweaking on the fly&quot; sizes=&quot;(min-width: 812px) 812px, 100vw&quot; width=&quot;2500&quot; height=&quot;1176&quot;&gt; &lt;/div&gt; &lt;/div&gt; &lt;figcaption&gt;My pattern tool allows a lot of tweaking on the fly&lt;/figcaption&gt; &lt;/figure&gt;
&lt;p&gt;Beyond patterns, it’s pretty much everything I use when drawing: pen and pencil tools, redraw-edge, line and star tools, a vector eraser, pathfinder add and subtract, offset path, Shape Builder for combining shapes by dragging across them.&lt;/p&gt;
&lt;p&gt;The list continues with multi-artboard documents with templates for new files, type support, mirror and anchor tools, proportional stroke scaling, vector brushes and art brushes, even a warp tool. It’s pretty feature complete.&lt;/p&gt;
&lt;figure&gt; &lt;div&gt; &lt;div&gt; &lt;img src=&quot;https://robertpaauwe.com/_astro/omen_closeup.CTOCwISC_1slkPc.webp&quot; srcset=&quot;https://robertpaauwe.com/_astro/omen_closeup.CTOCwISC_h5Ypf.webp 400w, https://robertpaauwe.com/_astro/omen_closeup.CTOCwISC_Z1QzeKw.webp 600w, https://robertpaauwe.com/_astro/omen_closeup.CTOCwISC_xXl6x.webp 900w, https://robertpaauwe.com/_astro/omen_closeup.CTOCwISC_1slkPc.webp 1137w&quot; alt=&quot;Close-up of the toolbar&quot; sizes=&quot;(min-width: 588px) 588px, 100vw&quot; width=&quot;1137&quot; height=&quot;1311&quot;&gt; &lt;/div&gt; &lt;/div&gt; &lt;figcaption&gt;Close-up of the toolbar&lt;/figcaption&gt; &lt;/figure&gt;
&lt;p&gt;One thing that wasn’t even part of the original plan: because every action gets logged into a persistent history file, the app can replay an entire illustration from blank canvas to finished piece and export that as a compressed video. I built it mostly to share process on social media, but there’s something satisfying about watching the playback.&lt;/p&gt;
&lt;figure&gt; &lt;div&gt; &lt;video src=&quot;https://robertpaauwe.com/_astro/omen_video.C4Y7tzsY.mp4&quot; autoplay muted loop playsinline preload=&quot;metadata&quot;&gt;&lt;/video&gt; &lt;/div&gt; &lt;figcaption&gt;Video export of the app, I did a quick sketch&lt;/figcaption&gt; &lt;/figure&gt;
&lt;h2 id=&quot;05-why-you-should-be-building-your-own-tools&quot;&gt;&lt;span&gt;05&lt;/span&gt; Why you should be building your own tools&lt;/h2&gt;
&lt;p&gt;I have built the perfect tool, for me. It has everything I need. And even though a few things could be better,&lt;sup&gt;[4]&lt;/sup&gt;  Omen is still better and tailored perfectly to &lt;strong&gt;what I need.&lt;/strong&gt; The cool thing about building your own tool is that you can always improve or change it later. If I get annoyed by something in the future or if it needs to be different, I can just add or change it.&lt;/p&gt;
&lt;aside&gt; &lt;p&gt;&lt;strong&gt;My takeaways&lt;/strong&gt;&lt;/p&gt; &lt;div&gt; &lt;p&gt;Building something like Omen is perfect to build yourself; it’s niche, the user group is small (only me), and it doesn’t need to operate on scale.&lt;/p&gt;&lt;br/&gt;&lt;p&gt;In roughly 7 days, I ended up with a tool that, for my needs, is &lt;strong&gt;significantly&lt;/strong&gt; better than any other tool on the market. On top of saving upwards of 500 euros per year, I can focus on getting the exact output that I want rather than trying to squeeze it out of existing tools through workarounds.&lt;/p&gt; &lt;/div&gt; &lt;/aside&gt;
&lt;p&gt;So where from here? I thought about open sourcing Omen. I’m not sure I’d be able to maintain it properly, as my life is busy as it is. I might bring Omen into a more generic shape so that I can open it to the public later. I don’t want to change Omen to a general purpose tool though, because adding more &lt;a href=&quot;https://robertpaauwe.com/blog/do-you-really-need-that-feature&quot;&gt;irrelevant features&lt;/a&gt; for me, bogs down my own workflow again.&lt;/p&gt;
&lt;p&gt;To be continued, below is a sneak peek of my next project.&lt;/p&gt;
&lt;figure&gt; &lt;div&gt; &lt;div&gt; &lt;img src=&quot;https://robertpaauwe.com/_astro/omen_dither.AJ7An1BI_ZmE25d.webp&quot; srcset=&quot;https://robertpaauwe.com/_astro/omen_dither.AJ7An1BI_2kmeuK.webp 400w, https://robertpaauwe.com/_astro/omen_dither.AJ7An1BI_1jIOau.webp 600w, https://robertpaauwe.com/_astro/omen_dither.AJ7An1BI_ZmE25d.webp 679w&quot; alt=&quot;Sneak preview of my next project&quot; sizes=&quot;(min-width: 588px) 588px, 100vw&quot; width=&quot;679&quot; height=&quot;455&quot;&gt; &lt;/div&gt; &lt;/div&gt; &lt;figcaption&gt;Sneak preview of my next project&lt;/figcaption&gt; &lt;/figure&gt;&lt;hr&gt;&lt;ol&gt;&lt;li&gt;Axidraw is a writing and drawing machine. I’ve got the V3/A3 and it is amazing. &lt;a href=&quot;https://axidraw.com/&quot; target=&quot;_blank&quot; rel=&quot;noopener noreferrer&quot;&gt;
Source
&lt;/a&gt;&lt;/li&gt;&lt;li&gt;Quiet Tarot has over 55k words of copy across its content&lt;/li&gt;&lt;li&gt;TLDraw is one of my favorite design tools. It’s simple, fast and perfect for throwaway designs. &lt;a href=&quot;https://tldraw.com/&quot; target=&quot;_blank&quot; rel=&quot;noopener noreferrer&quot;&gt;
Source
&lt;/a&gt;&lt;/li&gt;&lt;li&gt;The pencil tool is not that great. That took a long time to get sorta right. Particularly the “feel” of the pencil isn’t as good as Illustrator, Affinity, or Inkscape. It is usable, but lacks refinement. Type and the Live Trace tool is also kinda bare bones. It works, but it doesn’t have the same level of control as Illustrator’s Live Trace.&lt;/li&gt;&lt;/ol&gt;</content>
  </entry>
  <entry>
    <title>Do you really need that feature?</title>
    <link href="https://robertpaauwe.com/blog/do-you-really-need-that-feature/" rel="alternate" type="text/html" />
    <id>https://robertpaauwe.com/blog/do-you-really-need-that-feature/</id>
    <published>2026-08-28T00:00:00.000Z</published>
    <updated>2026-08-28T00:00:00.000Z</updated>
    <summary>When more really should be less.</summary>
    <category term="design-leadership" />
    <category term="product" />
    <content type="html">&lt;div&gt; &lt;span&gt;Note:&lt;/span&gt; This article was originally published on &lt;a href=&quot;https://rabobank.jobs/en/techblog/do-you-really-need-that-feature/&quot; target=&quot;_blank&quot; rel=&quot;noopener noreferrer&quot;&gt;Rabobank’s tech blog&lt;/a&gt; on 9 September 2021. I have rewritten and updated it here on 28 August 2026. &lt;/div&gt;
&lt;p&gt;Have you ever caught yourself, or your team, thinking: people like X, we should add X as a feature? Maybe a customer suggested it. Maybe marketing spotted a competitor doing it. More features feel like more value, surely that’s a safe bet?&lt;/p&gt;
&lt;p&gt;Every feature you ship is a permanent tax on your product: more surface area to navigate, more code to maintain, more decisions for users to make before they get to the thing they came for. More consequences for your product as a system. And usually, most of it never gets used.&lt;/p&gt;
&lt;p&gt;Pendo’s 2019 analysis of usage across more than 600 SaaS products found that just 12% of features drive 80% of daily usage.&lt;sup&gt;[1]&lt;/sup&gt;  The Standish Group found something similar back in 2002: roughly two-thirds of features in the average product go unused.&lt;sup&gt;[2]&lt;/sup&gt; &lt;/p&gt;
&lt;p&gt;Most of what feature teams build is potentially dead weight. So the real question isn’t “could this be a feature?” It’s “do we need it?”&lt;/p&gt;
&lt;h2 id=&quot;01-the-swiss-army-knife&quot;&gt;&lt;span&gt;01&lt;/span&gt; The Swiss Army Knife&lt;/h2&gt;
&lt;p&gt;Take the Swiss Army Knife. It’s a great product with a lot of tools packed into a small space, and it earns that density because of the context it’s built for: survival and camping, where carrying a full toolbox isn’t an option. Tiny scissors beat no scissors. But your hairdresser isn’t reaching for the Swiss Army Knife’s scissors to cut your hair.&lt;/p&gt;
&lt;p&gt;The Swiss Army Knife does a lot of things, but nothing as well as the dedicated version of that thing does it. That’s the deal you make in exchange for portability, and it’s a good deal when you’re out in the wilderness.&lt;/p&gt;
&lt;p&gt;Most products aren’t being used in the wilderness. Your users usually have other tools within reach, so bundling doesn’t earn the same goodwill it earns a multitool in a backpack. Context decides whether a broad feature set is a strength or a liability, and most teams never stop to ask which one they’re in.&lt;/p&gt;
&lt;h2 id=&quot;02-the-power-of-removal&quot;&gt;&lt;span&gt;02&lt;/span&gt; The power of removal&lt;/h2&gt;
&lt;p&gt;Add enough features and you get feature bloat: a slow entropy where the product’s original shape disappears under everything that’s been layered on top. Strap ten car-repair tools onto the Swiss Army Knife and it stops being a pocket multitool. It becomes a heavy, confusing object that does everything a little worse than it did the one thing it used to do well.&lt;/p&gt;
&lt;p&gt;I used to think of this mostly as a discipline problem: nobody says no and bloat creeps in. But there’s research suggesting it goes deeper than that. Gabrielle Adams and colleagues at the University of Virginia ran a series of studies, published in Nature in 2021 and later expanded by co-author Leidy Klotz into the book &lt;em&gt;Subtract&lt;/em&gt;, and found that when people are asked to improve something, they reach for addition almost every time, even when removing something would clearly work better.&lt;sup&gt;[3]&lt;/sup&gt; &lt;/p&gt;
&lt;p&gt;In one study, people improving an overloaded New York itinerary barely ever removed anything from it. Most only started cutting items once the researchers explicitly reminded them that “improve” could mean taking things away, not just piling more on.&lt;/p&gt;
&lt;figure&gt; &lt;blockquote&gt; &lt;p&gt;Bloat is rarely intentional; it happens by default as your product experiences entropy.&lt;/p&gt; &lt;/blockquote&gt;  &lt;/figure&gt;
&lt;p&gt;Have you ever been in a meeting where the purpose was to build something? The goal was to ship something. Every addition feels like obvious progress in the room, while removal has to be proposed on purpose, defended, and often re-justified.&lt;/p&gt;
&lt;p&gt;Addition is just easier.&lt;/p&gt;
&lt;h2 id=&quot;03-removing-is-designing-too&quot;&gt;&lt;span&gt;03&lt;/span&gt; Removing is designing too&lt;/h2&gt;
&lt;p&gt;As designers, we’re wired to create: a new feature to delight customers, a new flow to win new ones. But think about the last time you removed something from a live product to make it better. Not in a design review, in production, after people were already relying on it. For most of us, that’s a really short list.&lt;/p&gt;
&lt;p&gt;Once a feature ships, it’s hard to kill. The business feels like it already invested time and money into it, and now removing it costs more time and money on top of that. There’s almost always a small group of people who love it, however little it’s used, and they tend to be loud precisely because they’re the ones still there.&lt;/p&gt;
&lt;figure&gt; &lt;blockquote&gt; &lt;p&gt;Somebody using a feature isn’t the same as that feature belonging in your product.&lt;/p&gt; &lt;/blockquote&gt;  &lt;/figure&gt;
&lt;p&gt;Internally it’s an awkward conversation too: someone championed this feature once, it might still be tied to their performance review, and telling them their project is getting cut isn’t a meeting anyone volunteers to run. The longer a feature survives, the harder and more expensive it gets to remove, which is a big part of why so few teams ever get around to it, and why bloat tends to build up rather than reset.&lt;/p&gt;
&lt;p&gt;Cutting a feature you don’t need is good design. Cutting it without warning, without a migration path, without an explanation, ends up costing you almost as much goodwill as never cutting it at all.&lt;/p&gt;
&lt;p&gt;Cutting bloat is design work, and it deserves the same celebration as shipping new stuff.&lt;/p&gt;
&lt;h2 id=&quot;04-how-to-make-subtraction-routine&quot;&gt;&lt;span&gt;04&lt;/span&gt; How to make subtraction routine&lt;/h2&gt;
&lt;p&gt;So what’s your product’s central proposition? What problem are you solving, for whom, in what context? &lt;a href=&quot;https://steveblank.com/2011/09/22/how-to-build-a-web-startup-lean-launchpad-edition/&quot;&gt;Steve Blank’s format&lt;/a&gt; still works well here: we help (X) do (Y) by doing (Z).&lt;/p&gt;
&lt;p&gt;Take a banking app. Say you’ve learned your customers are constantly on the move and need to pay quickly while commuting. The central proposition might be simple: we help our customers save time by making payments fast. QR-code payments and Apple Pay support that directly. A photo-sharing feature or an in-app gift shop might delight someone, somewhere, but neither one defends itself against that proposition.&lt;/p&gt;
&lt;p&gt;Test every idea against that statement, and be honest about the answer. Does this support what we’re trying to do, or are we just excited about it? Is it a logical extension of the core, or could we simply skip it? If you can’t answer that in a sentence, you probably already have your answer.&lt;sup&gt;[4]&lt;/sup&gt; &lt;/p&gt;
&lt;p&gt;I have collected a few habits to make this line of thinking part of your regular routine in product development:&lt;/p&gt;
&lt;aside&gt; &lt;p&gt;&lt;strong&gt;SOME USEFUL HABITS&lt;/strong&gt;&lt;/p&gt; &lt;div&gt; &lt;ul&gt;
&lt;li&gt;Give every feature a reason to exist that you could later prove wrong. Write it as one sentence at launch, using the same central-proposition test above. If nobody on the team can write that sentence, that’s worth thinking about.&lt;/li&gt;
&lt;li&gt;Also review features on a trigger, not only on a date or fixed interval. If usage drops under a certain threshold, put it up for a “defend, improve or deprecate” conversation.&lt;/li&gt;
&lt;li&gt;Treat deprecation as its own design problem. A better product sometimes means removing bloat and restructuring.&lt;/li&gt;
&lt;li&gt;Not building something is worth celebrating. A “no” to a pitch or concept sometimes means a better product as a result. Preventing something from being built creates an opportunity to contribute to the core value proposition instead.&lt;/li&gt;
&lt;/ul&gt; &lt;/div&gt; &lt;/aside&gt;
&lt;div&gt; &lt;p&gt;Pushing back on my own argument&lt;/p&gt; &lt;div&gt; &lt;p&gt;Cutting things isn’t automatically good design just because it’s cutting. It’s easy to be careless about how you remove something, and that failure mode is just as real as bloat itself. Google has a habit of abruptly killing products: Reader, Inbox, Stadia, and a long list of others. It has spawned an entire watchdog site&lt;sup&gt;[5]&lt;/sup&gt;  and it’s dented trust in Google’s newer products, because people learned that betting on a Google tool carries real risk of it vanishing with little warning.&lt;/p&gt; &lt;/div&gt; &lt;/div&gt;
&lt;p&gt;None of this makes it painless to kill something people rely on.&lt;sup&gt;[6]&lt;/sup&gt;  But here is my challenge to you. Think of removal as a normal, expected part of doing product design.&lt;/p&gt;
&lt;p&gt;What would you remove from your product to make it better?&lt;/p&gt;
&lt;h2 id=&quot;05-further-reading&quot;&gt;&lt;span&gt;05&lt;/span&gt; Further reading&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Adams, Converse, Hales &amp;amp; Klotz, &lt;a href=&quot;https://www.nature.com/articles/s41586-021-03380-y&quot;&gt;“People systematically overlook subtractive changes,”&lt;/a&gt; &lt;em&gt;Nature&lt;/em&gt; 592 (2021). The study behind the “we default to adding” argument.&lt;/li&gt;
&lt;li&gt;Leidy Klotz, &lt;a href=&quot;https://behavioralscientist.org/subtract-why-getting-to-less-can-mean-thinking-more/&quot;&gt;&lt;em&gt;Subtract: The Untapped Science of Less&lt;/em&gt;&lt;/a&gt; (2021). The book-length version, with more examples across design, writing, and policy.&lt;/li&gt;
&lt;li&gt;Pendo, &lt;a href=&quot;https://www.pendo.io/resources/the-2019-feature-adoption-report/&quot;&gt;&lt;em&gt;2019 Feature Adoption Report&lt;/em&gt;&lt;/a&gt;. The 12%/80% usage-concentration data point.&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://www.nngroup.com/articles/product-ux-glossary/&quot;&gt;Nielsen Norman Group on feature creep and feature bloat&lt;/a&gt;. The usability angle on the same problem.&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://killedbygoogle.com&quot;&gt;Killed by Google&lt;/a&gt;. A running, slightly gleeful catalog of what happens when subtraction is done without care for trust.&lt;/li&gt;
&lt;li&gt;Basecamp’s &lt;a href=&quot;https://basecamp.com/shapeup&quot;&gt;&lt;em&gt;Shape Up&lt;/em&gt;&lt;/a&gt; on shipping less and saying no.&lt;/li&gt;
&lt;li&gt;Marty Cagan, &lt;a href=&quot;https://www.svpg.com/books/inspired-how-to-create-tech-products-customers-love-2nd-edition/&quot;&gt;&lt;em&gt;Inspired&lt;/em&gt;&lt;/a&gt;. On product management as mostly the discipline of deciding what not to build.&lt;/li&gt;
&lt;li&gt;Barry Schwartz, &lt;a href=&quot;https://en.wikipedia.org/wiki/The_Paradox_of_Choice&quot;&gt;&lt;em&gt;The Paradox of Choice&lt;/em&gt;&lt;/a&gt;. The psychological backdrop for why more options can make products, and people, worse off, not better.&lt;/li&gt;
&lt;/ul&gt;&lt;hr&gt;&lt;ol&gt;&lt;li&gt;Pendo, 2019 Feature Adoption Report. &lt;a href=&quot;https://www.pendo.io/resources/the-2019-feature-adoption-report/&quot; target=&quot;_blank&quot; rel=&quot;noopener noreferrer&quot;&gt;
Source
&lt;/a&gt;&lt;/li&gt;&lt;li&gt;Widely cited as “64% of features are rarely or never used.” Worth knowing the number traces back to a small internal study, not a broad industry survey, though the general pattern still holds up across later research. &lt;a href=&quot;https://www.mountaingoatsoftware.com/blog/are-64-of-features-really-rarely-or-never-used&quot; target=&quot;_blank&quot; rel=&quot;noopener noreferrer&quot;&gt;
Source
&lt;/a&gt;&lt;/li&gt;&lt;li&gt;Adams, Converse, Hales &amp;amp; Klotz, “People systematically overlook subtractive changes,” Nature 592 (2021). &lt;a href=&quot;https://www.nature.com/articles/s41586-021-03380-y&quot; target=&quot;_blank&quot; rel=&quot;noopener noreferrer&quot;&gt;
Source
&lt;/a&gt;&lt;/li&gt;&lt;li&gt;The proposition itself deserves scrutiny too, probably even more so. Products evolve and contexts shift, and a proposition that was right three years ago can go stale fast.&lt;/li&gt;&lt;li&gt;Killed by Google: a running catalog of discontinued Google products, currently over 250 and counting. &lt;a href=&quot;https://killedbygoogle.com&quot; target=&quot;_blank&quot; rel=&quot;noopener noreferrer&quot;&gt;
Source
&lt;/a&gt;&lt;/li&gt;&lt;li&gt;There is an emotional aspect that you can’t ignore. There are always people who worked on the feature before.&lt;/li&gt;&lt;/ol&gt;</content>
  </entry>
  <entry>
    <title>New site, new blog</title>
    <link href="https://robertpaauwe.com/blog/starting-this-blog/" rel="alternate" type="text/html" />
    <id>https://robertpaauwe.com/blog/starting-this-blog/</id>
    <published>2026-08-17T00:00:00.000Z</published>
    <updated>2026-08-17T00:00:00.000Z</updated>
    <summary>Back to writing things down.</summary>
    <category term="meta" />
    <content type="html">&lt;p&gt;My old website ran on WordPress, and over time it turned into something I avoided touching. Changing layouts was a real struggle: wrestling with a pre-built theme meant massive CSS overrides just to get, sort of, what I wanted.&lt;/p&gt;
&lt;p&gt;Basic site management, plugin updates, the occasional broken thing, made me hesitant to even open the site. I stopped working on it altogether.&lt;/p&gt;
&lt;h2 id=&quot;01-what-i-really-wanted&quot;&gt;&lt;span&gt;01&lt;/span&gt; What I really wanted&lt;/h2&gt;
&lt;p&gt;Not much. &lt;sup&gt;[1]&lt;/sup&gt;  A simple publishing flow that has writing and getting it live at roughly the same effort. I like Markdown and &lt;a href=&quot;https://en.wikipedia.org/wiki/LaTeX&quot;&gt;LaTeX&lt;/a&gt; for that reason. I also wanted control of layout and design. So I can change myself in code, without constantly wrestling with a bulky theme system.&lt;/p&gt;
&lt;p&gt;That’s why I picked &lt;a href=&quot;https://astro.build/&quot;&gt;Astro&lt;/a&gt; to rebuild my personal website. Astro’s a static site generator built around a simple workflow: write a document, drop it in a folder, and Astro takes care of the formatting. It’s similar, in spirit, to a publishing workflow I designed for &lt;a href=&quot;https://robertpaauwe.com/projects/atrias&quot;&gt;Atrias&lt;/a&gt; a few years ago.&lt;/p&gt;
&lt;p&gt;No database, no admin panel, no plugin ecosystem to keep patched. Where I do want something interactive, it slots in as a self-contained component on just that page. I’m curious to see how it performs once I start integrating some &lt;a href=&quot;https://hourlyinvasion.tumblr.com/&quot;&gt;weird tools&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;I’m happy with the result: plain static files that load fast.&lt;/p&gt;
&lt;figure&gt; &lt;div&gt; &lt;div&gt; &lt;img src=&quot;https://robertpaauwe.com/_astro/hourly-invasion.uv2ua4SY_dGsGS.webp&quot; srcset=&quot;https://robertpaauwe.com/_astro/hourly-invasion.uv2ua4SY_8Wcbl.webp 400w, https://robertpaauwe.com/_astro/hourly-invasion.uv2ua4SY_1bYpo2.webp 600w, https://robertpaauwe.com/_astro/hourly-invasion.uv2ua4SY_hze4B.webp 900w, https://robertpaauwe.com/_astro/hourly-invasion.uv2ua4SY_Z20Q3IA.webp 1200w&quot; alt=&quot;A grid of randomly colored pixel-art space invaders, each with a unique number and color code&quot; sizes=&quot;(min-width: 812px) 812px, 100vw&quot; width=&quot;1440&quot; height=&quot;737&quot;&gt; &lt;/div&gt; &lt;/div&gt; &lt;figcaption&gt;One of the weird tools waiting to get wired in: a bot that generates a new, uniquely numbered space invader every hour.&lt;/figcaption&gt; &lt;/figure&gt;
&lt;h2 id=&quot;02-out-with-the-old&quot;&gt;&lt;span&gt;02&lt;/span&gt; Out with the old&lt;/h2&gt;
&lt;p&gt;Rebuilding the site was also a good excuse&lt;sup&gt;[2]&lt;/sup&gt;  to refresh the rest of it: my portfolio, my illustration work, my typefaces. As most designers know, reworking a portfolio is a ****-load of work.&lt;/p&gt;
&lt;p&gt;To give you an idea of the contrast: rewriting the portfolio’s content was ten times the work of setting up Astro, building all the components, and designing the site.&lt;/p&gt;
&lt;p&gt;Redoing a portfolio is one of those tasks I always postpone until I need it.&lt;sup&gt;[3]&lt;/sup&gt;  Then I have to scramble to figure out what needs updating, and the result is always rushed. I hadn’t looked at mine in close to five years. It needed real work.&lt;/p&gt;
&lt;h2 id=&quot;03-read-more-write-more&quot;&gt;&lt;span&gt;03&lt;/span&gt; Read more, write more&lt;/h2&gt;
&lt;p&gt;So the plan from here: write more on the things that keep me busy. Design, systems thinking, platforms, and what design leadership actually looks like inside complex, large organizations. And whatever else I happen to be making in my free time, since that’s usually where the more interesting thinking happens anyway.&lt;/p&gt;
&lt;p&gt;So no fixed schedule, no fixed theme. Partly, this is a habit I want to rebuild: keeping better track of what I’m reading, thinking, and making. And to become a better writer.&lt;/p&gt;
&lt;p&gt;Let’s see where it goes.&lt;sup&gt;[4]&lt;/sup&gt; &lt;/p&gt;&lt;hr&gt;&lt;ol&gt;&lt;li&gt;Okay, done!&lt;/li&gt;&lt;li&gt;Well, it wasn’t really an excuse. I was throwing away my old site, so I was kind of forced to redo it.&lt;/li&gt;&lt;li&gt;I didn’t &lt;em&gt;really&lt;/em&gt; need a new portfolio right now. The luxury of not having any pressure allowed me to take my time and finish it on my own terms.&lt;/li&gt;&lt;li&gt;Let me know if you find some bugs, I’d love to fix them.&lt;/li&gt;&lt;/ol&gt;</content>
  </entry>
</feed>
