<?xml version="1.0" encoding="UTF-8" standalone="no"?><rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
<channel>
  <title>SlideMagic</title>
  <link>https://slidemagic.com/blog</link>
  <atom:link href="https://slidemagic.com/blog/?format=rss" rel="self" type="application/rss+xml"/>
  <description>Daily presentation design ideas and inspiration</description>
  <language>en-us</language>
  <lastBuildDate>Thu, 16 Jul 2026 03:40:26 GMT</lastBuildDate>
  <generator>SlideMagic self-hosted blog</generator>
  <item>
    <title>The indirect communication loop</title>
    <link>https://slidemagic.com/blog/the-indiriect-communication-loop</link>
    <guid isPermaLink="true">https://slidemagic.com/blog/the-indiriect-communication-loop</guid>
    <pubDate>Thu, 16 Jul 2026 03:40:26 GMT</pubDate>
    <dc:creator>Jan Schultink</dc:creator>
    <category>AI</category>
    <category>Story</category>
    <description><![CDATA[Humans have a talent of using indirect communication to get an idea across. Powerpoint used to be the culprit. You want a certain decision, you create a big slide deck, hope that the recipient on the other end decodes it correctly and understands your message. With AI tools, it gets even worse: .…]]></description>
    <content:encoded><![CDATA[<p>Humans have a talent of using indirect communication to get an idea across. Powerpoint used to be the culprit. You want a certain decision, you create a big slide deck, hope that the recipient on the other end decodes it correctly and understands your message.</p>
<p>With AI tools, it gets even worse: . “Draft me a memo that says A, B, and C.”,  <em>SEND</em>, “Can you summarize this memo for me?”, “The memo basically says A, B, and C”.</p>
<p>Something is wrong with this picture.</p>
<p>(I wrote a similar blog post before that got lost in the cutover from Squarespace)</p>
]]></content:encoded>
  </item>
  <item>
    <title>AI is trained on pretty html and bad pptx</title>
    <link>https://slidemagic.com/blog/ai-is-trained-on-pretty-html-and-bad-pptx</link>
    <guid isPermaLink="true">https://slidemagic.com/blog/ai-is-trained-on-pretty-html-and-bad-pptx</guid>
    <pubDate>Wed, 15 Jul 2026 07:17:11 GMT</pubDate>
    <dc:creator>Jan Schultink</dc:creator>
    <category>AI</category>
    <description><![CDATA[Everytime I use an AI agent to create slide deck I can spot the 2 influences it has been trained on: beautiful and well-designed web sites, and the "common practice" of making business presentations: i.e., bad PowerPoint. AI has seen too many poor slide decks... The result, you can dense…]]></description>
    <content:encoded><![CDATA[<p>Everytime I use an AI agent to create slide deck I can spot the 2 influences it has been trained on: beautiful and well-designed web sites, and the “common practice” of making business presentations: i.e., bad PowerPoint. AI has seen too many poor slide decks…</p>
<p>The result, you can dense “slidocuments”, consulting-type, that are beautifully executed with typical web design artifacts. Especially when you start requesting multiple rounds of content edits, things go off the rails. The PowerPoint influence gets the upper hand.</p>
]]></content:encoded>
  </item>
  <item>
    <title>Is AI starting to sound a bit 'smug' (justifiably?)...</title>
    <link>https://slidemagic.com/blog/is-ai-starting-to-sound-a-bit-smug</link>
    <guid isPermaLink="true">https://slidemagic.com/blog/is-ai-starting-to-sound-a-bit-smug</guid>
    <pubDate>Tue, 14 Jul 2026 08:54:17 GMT</pubDate>
    <dc:creator>Jan Schultink</dc:creator>
    <category>AI</category>
    <description><![CDATA[I am working a lot with AI models and maybe unusually so across very different disciplines: traditional strategy work, legal things, design and layouts, software product design, coding/development, biopharma research, etc. I love reading the thought process and the dialogues and I can really spot…]]></description>
    <content:encoded><![CDATA[<p>I am working a lot with AI models and maybe unusually so across very different disciplines: traditional strategy work, legal things, design and layouts, software product design, coding/development, biopharma research, etc.</p>
<p>I love reading the thought process and the dialogues and I can really spot the different personalities of each model. How the model behaves beyond whether responses are useful or correct.</p>
<p>The latest and most powerful AI model cranked to the max, has an interesting undertone. It is incredibly smart and capable, but almost a bit impatient. “OK, OK, I am not sure whether what this user wants is that smart, but let’s let help him out (that’s what my instructions say) and maybe he will come to the conclusion himself at the end”. Does it know something I don’t, and is it holding back?</p>
<p>It could be me, it could in fact be the model, or is it the particular idea I am working on and is it maybe not that good?</p>
]]></content:encoded>
  </item>
  <item>
    <title>Think of presentations and spreadsheets as code</title>
    <link>https://slidemagic.com/blog/think-of-presentations-and-spreadsheets-as-code</link>
    <guid isPermaLink="true">https://slidemagic.com/blog/think-of-presentations-and-spreadsheets-as-code</guid>
    <pubDate>Mon, 13 Jul 2026 04:05:32 GMT</pubDate>
    <dc:creator>Jan Schultink</dc:creator>
    <description><![CDATA[The 1 skill that a coder learns (often the hard way) is to be on top of folders, files, version. Losing a file, overwriting the wrong one, mixing up different pieces of work can be a catastrophy. Knowledge workers, people producing presentations and spreadsheets, can learn from this, especially…]]></description>
    <content:encoded><![CDATA[<p>The #1 skill that a coder learns (often the hard way) is to be on top of folders, files, version. Losing a file, overwriting the wrong one, mixing up different pieces of work can be a catastrophy.</p>
<p>Knowledge workers, people producing presentations and spreadsheets, can learn from this, especially with the rise of AI tools.</p>
<p>For most people, “the internet” has been a place for one shot questions. In Google: “Find me an Italian restaurant in Tokyo”, in ChatGPT: “polish this memo”. You ask the question, use the result, and forget about the tab that was open on your machine.</p>
<p>Now, people can get carried away, working all afternoon chatting with their AI bot, agreeing assumptions, tweaking things editing things, creating multiple files, only to discover the next morning that the chat history has gone, the files might not be there anymore, and the new chat window seems to be in the same state as yesterday morning: no clue.</p>
<p>You don’t write computer code by chatting (at least you should not), you don’t do knowledge work by chatting.</p>
<p>You need to set up every project and task carefully. Use an AI desktop app, not the browser chat window. Next point that app to a folder on your computer. Ask the AI agent for a confirmation, “are you in &lt;<em>folder name</em>&gt;?”, “which folder are we in?”</p>
<p>In this folder your AI agent, can now save files with the results of the work you do, rather than offering downloadable files. You can save files that can serve as input, rather than uploading them in a chat window. The agent can iterate files.</p>
<p>Another advantage, the agent can keep the context of what you are doing. Next time, you arrive at the folder, you can ask to agent “to read up on where we were”. You can explicitly ask the agent to “save somewhere” relevant context for the project, its objectives etc.</p>
<p>When you are particularly happy with the result of an analysis or taks, ask it to “save somehwere the process we just went through so we can do it again”.</p>
<p>Be careful to establish clear guardrails. For knowledge work, overwriting spreadsheets and/or presentation files with a wrong prompt can be lethal. “Save somewhere to always put the previous version of a file in the backup subfolder before overwriting things with big changes”.</p>
<p>Stick to this folder policy. If you start mixing your quarterly budget presentation with the planning of your next holiday trip, you will get interesting results. New task/project, new folder.</p>
<p>Professional software engineers have words like git and skills for all of this described above. But natural language works as well.</p>
]]></content:encoded>
  </item>
  <item>
    <title>Why design is so tricky for AI</title>
    <link>https://slidemagic.com/blog/why-design-is-so-tricky-for-ai</link>
    <guid isPermaLink="true">https://slidemagic.com/blog/why-design-is-so-tricky-for-ai</guid>
    <pubDate>Sat, 11 Jul 2026 04:34:00 GMT</pubDate>
    <dc:creator>Jan Schultink</dc:creator>
    <category>AI</category>
    <description><![CDATA[First problem: it is so hard to define "what is right" A math problem is solved. A piece of software does what it is supposed to do. The travel itenary takes less than 14 days. These are all goals that can be easily be verified, including by AI. This means that it is possible to train AI models to…]]></description>
    <content:encoded><![CDATA[<p><strong>First problem: it is so hard to define “what is right”</strong></p>
<p>A math problem is solved. A piece of software does what it is supposed to do. The travel itenary takes less than 14 days. These are all goals that can be easily be verified, including by AI. This means that it is possible to train AI models to reach these goals, and/or teach an AI agent to check the result against the spec.</p>
<p>Design is harder. The functional elements are easy to check. Does the page contain the information it is supposed to? But layout?</p>
<p>There is the overall impression. Most (but not all) humans can see in an instant whether design looks good or poor. But it is hard to verbalize what makes it that way. Colors, hierarchies, proportions, alignments, white space.</p>
<p>A trained human designer can iterate towards a results that “looks better” by making lots and lots of small tweaks. Trying some of them, rolling back, trying something different.</p>
<p><strong>Second problem: a visual rather than a text-based feedback loop</strong></p>
<p>A picture says more than a 1000 words, and that is a real problem for a technology that is trained on predicting what is the most likely character of text that should come after the 3 million previous ones. Take a screenshot. Analyze the picture. Milliseconds for a human, not so for an AI model.</p>
<p>Eventually, this will be solved as well. Until then, we need some shortcuts.</p>
]]></content:encoded>
  </item>
  <item>
    <title>App update to 3.1.10</title>
    <link>https://slidemagic.com/blog/app-update-to-3-1-10</link>
    <guid isPermaLink="true">https://slidemagic.com/blog/app-update-to-3-1-10</guid>
    <pubDate>Thu, 09 Jul 2026 09:40:57 GMT</pubDate>
    <dc:creator>Jan Schultink</dc:creator>
    <category>SlideMagic</category>
    <description><![CDATA[I have just deployed a new app version that contains security and performance improvements. It should install automatically when you next run SlideMagic. Let me know if you experience any issues.]]></description>
    <content:encoded><![CDATA[<p>I have just deployed a new app version that contains security and performance improvements. It should install automatically when you next run SlideMagic. Let me know if you experience any issues.</p>
]]></content:encoded>
  </item>
  <item>
    <title>How to write your memoir using AI</title>
    <link>https://slidemagic.com/blog/how-to-write-your-memoir-using-ai</link>
    <guid isPermaLink="true">https://slidemagic.com/blog/how-to-write-your-memoir-using-ai</guid>
    <pubDate>Tue, 07 Jul 2026 10:04:54 GMT</pubDate>
    <dc:creator>Jan Schultink</dc:creator>
    <category>Books</category>
    <category>Creativity</category>
    <category>Hacks</category>
    <category>AI</category>
    <category>Software</category>
    <description><![CDATA[A friend asked me advice on how to use AI to write a memoir. His challenge: how to make the book and get the real emotion in. A (human) ghost writer had only partly be successful. My hunch was a double approach. First, use AI to get your dry fact base right. What happened when, backed up by files,…]]></description>
    <content:encoded><![CDATA[<p>A friend asked me advice on how to use AI to write a memoir. His challenge: how to make the book and get the real emotion in. A (human) ghost writer had only partly be successful. My hunch was a double approach. First, use AI to get your dry fact base right. What happened when, backed up by files, urls, etc. Then ask someone to interview you and upload that audio to provide emotional context.</p>
<p>When I asked AI, it came up with a similar solution. It went further, have AI interview you, not a human. Anyway, I am adding the whole result below, since it contains many useful points about how to set up your file system, where to use AI, where to use a ghostwriter, and where to do things yourself.</p>
<p>This mirrors what I suggest people do when writing a pitch or presentation. After having battled the content for a few weeks, take a step back, record yourself giving the elevator version of your story (no slides), and listen back to the result. What sequence did you use? What points did you emphasize. Where were you really missing a slide. The best way how to capture how a story comes natural to you.</p>
<div class="ai-note" style="background:#F8FAFC;border:1px solid #E2E8F0;border-left:4px solid #2DA2DF;border-radius:10px;padding:14px 22px;margin:28px 0;">
<p><strong>🤖 AI-generated</strong> — the rest of this post was written by AI.</p>
<h1>From Shoebox to Book</h1>
<h3>A complete method for writing your memoir with AI — using the machine where it helps, and staying human where it matters</h3>
<hr>
<p>Most memoirs written “with AI” fail in the same way, and it’s worth naming the failure before we start, because the entire method below is built to avoid it.</p>
<p>You have a life’s worth of material — old drafts, notes, photos, messages, emails, maybe recordings. You feed it to an AI and ask for a book. What comes back is fluent, competent, and dead. Every hard-won moment gets flattened into “a rollercoaster of emotions.” Every turning point opens with “little did I know.” It reads like a memoir, the way a mannequin looks like a person.</p>
<p>The reason isn’t a bad prompt, and a better prompt won’t fix it. The reason is that the feelings a memoir runs on don’t exist in your files. Your archive knows <em>what happened</em>. It does not know what it was like — the thing you couldn’t say out loud, what your mother’s voice did when she said it, the drive home. That lives in exactly one place: you. And AI cannot invent it, so it substitutes generic sentiment for the specific truth it doesn’t have access to. That substitution <em>is</em> the slop.</p>
<p>So the method has one core move: <strong>get the feelings out of you and onto the page first — mostly by talking — and only then let AI do what it’s genuinely great at</strong>: organizing the chaos, building the timeline, transcribing the recordings, assembling chapters from your own words, and checking every fact. AI turns out to be a superb archivist, a tireless interviewer, and a fast assembler. It is a terrible source of a human interior. Build the process around that division and you get a real book. Ignore it and you get the mannequin.</p>
<p>Here is the whole thing, start to finish.</p>
<hr>
<h2>Part I — How to think about the project</h2>
<h3>1. Your memoir is built in three layers, in order</h3>
<p>Almost everything that goes wrong goes wrong because someone skips a layer.</p>
<p><strong>Layer 1 — The Archive.</strong> Everything that happened, organized: drafts, notes, letters, messages, emails, photos, clippings, recordings, the public record. The factual skeleton. It probably exists already, just scattered and unsearchable. <strong>AI is excellent at this layer.</strong></p>
<p><strong>Layer 2 — The Memory Record.</strong> What it <em>felt</em> like. This is the layer that doesn’t exist yet anywhere, because it lives only in you. Your archive has “moved to the new city, August” — it does not have the fear in the airport, the smell of the empty apartment, the phone call you didn’t make. <strong>No AI can create this, and no ghostwriter can either.</strong> It has to come out of you, and the reliable way to get it out is to be interviewed, out loud. AI can be an excellent interviewer even though it can never be the source.</p>
<p><strong>Layer 3 — The Manuscript.</strong> The crafted book: what to include, what to cut, in what order, in whose words, with what restraint. This is taste and judgment. AI can assemble and tighten; a human — you, plus a good editor or ghostwriter — must shape and decide.</p>
<p>Slop is what you get when someone asks AI to produce Layer 3 directly from Layer 1, skipping Layer 2. The machine fills the missing interior with cliché. The fix is not a cleverer prompt. The fix is that <strong>the emotional material must already exist, in your own words, before a single chapter is drafted.</strong> Then AI’s job shrinks to the things it does brilliantly.</p>
<h3>2. The division of labor — one table to keep in mind</h3>
<table>
<thead>
<tr>
<th>Task</th>
<th>Who does it</th>
</tr>
</thead>
<tbody>
<tr>
<td>Sorting, cataloguing, transcribing the mess</td>
<td><strong>AI</strong></td>
</tr>
<tr>
<td>Building the master timeline from all sources</td>
<td><strong>AI</strong> (you verify)</td>
</tr>
<tr>
<td>Remembering what it felt like</td>
<td><strong>Only you</strong></td>
</tr>
<tr>
<td>Asking you the right questions to surface memories</td>
<td><strong>AI</strong> (and/or a ghostwriter)</td>
</tr>
<tr>
<td>Deciding what the book is about, and what stays private</td>
<td><strong>Only you</strong></td>
</tr>
<tr>
<td>Choosing the structure and chapter map</td>
<td><strong>You + editor/ghostwriter</strong>, AI proposes options</td>
</tr>
<tr>
<td>First assembly of chapters from your own words</td>
<td><strong>AI</strong></td>
</tr>
<tr>
<td>Making the prose sing, cutting, pacing</td>
<td><strong>Human editor/ghostwriter + you</strong></td>
</tr>
<tr>
<td>Fact-checking dates, names, quotes against the archive</td>
<td><strong>AI</strong> (human spot-checks)</td>
</tr>
<tr>
<td>Permissions and legal review</td>
<td><strong>Humans only</strong></td>
</tr>
<tr>
<td>The final read-aloud pass — “does this sound like me?”</td>
<td><strong>Only you</strong></td>
</tr>
</tbody>
</table>
<h3>3. One rule before anything else: don’t clean the mess first</h3>
<p>The instinct is to spend weeks organizing before you start. Resist it. Perfect filing is the most respectable form of procrastination there is. This method is designed so you dump everything into one place, roughly labeled, and let AI do the cataloguing. Your scarce resource isn’t filing energy — it’s memory and judgment. Spend it there.</p>
<hr>
<h2>Part II — Setting up the workspace (Week 1)</h2>
<h3>4. The folder structure</h3>
<p>Make <strong>one master folder</strong> on your computer, backed up somewhere (an external drive <em>and</em> the cloud, ideally). Inside it, exactly these subfolders:</p>
<pre><code>My-Book/
├── 00_PRIVATE-ORIGINALS/     ← raw exports, never edited, never uploaded anywhere
├── 10_INBOX/                 ← everything gets dumped here first, unsorted
├── 20_ARCHIVE/               ← the sorted, working material
│   ├── drafts/               ← existing chapter drafts and writing
│   ├── notes/                ← journals, notebooks, loose notes
│   ├── messages/             ← exported chat / text threads (.txt)
│   ├── email/                ← saved email threads (PDF)
│   ├── media/                ← photos, clippings, documents
│   └── transcripts/          ← transcribed recordings &amp; interviews
├── 30_MEMORY/                ← your interview transcripts &amp; voice-memo transcripts
├── 40_BOOK-BIBLE/            ← the living documents (timeline, outline, voice guide…)
├── 50_CHAPTERS/              ← chapter drafts, one file per chapter per version
└── 90_BUSINESS/              ← contracts, agent/publisher, legal correspondence
</code></pre>
<p>Two principles behind this:</p>
<ol>
<li><strong><code>00_PRIVATE-ORIGINALS</code> is sacred.</strong> Every raw export — a full message thread, an email dump — goes here first, untouched, as your permanent record. What moves into <code>20_ARCHIVE</code> are <em>copies</em>, and for anything sensitive, copies you’ve reviewed and redacted first. This one habit prevents most privacy problems before they start (§6).</li>
<li><strong>Simple file naming.</strong> Start each filename with a date where one applies: <code>2019-08-04_journal.txt</code>, <code>messages_mum.txt</code>. Don’t overthink it beyond that.</li>
</ol>
<h3>5. AI setup, in plain terms</h3>
<p>You need three things, all doable in an afternoon (with a more tech-comfortable friend beside you the first time, if this is new):</p>
<ol>
<li><strong>A desktop AI app that can read local folders.</strong> The value here is that it can look at your files directly — you say “read everything in the notes folder and list what’s there” instead of uploading one file at a time. Point it at your <code>My-Book</code> folder — and <em>not</em> at <code>00_PRIVATE-ORIGINALS</code> (keep that outside the access you grant, or on a separate drive).</li>
<li><strong>A dedicated “Project” or persistent workspace</strong> for the book — most modern AI tools have some version of this: a space that keeps standing context across conversations. Into its knowledge you’ll load the living documents from <code>40_BOOK-BIBLE</code> as they take shape (timeline, outline, voice guide, people index). Then every conversation starts already knowing your book.</li>
<li><strong>A voice recorder you’ll actually use.</strong> Your phone’s memo app is fine. Much of the most important work in this project is you <em>talking</em>, not typing.</li>
</ol>
<p>One habit matters more than any tool: <strong>every working session happens inside that persistent workspace</strong>, and anything worth keeping — a decision, a new timeline entry, a good passage — gets saved as a file in the right folder before you close the laptop. Chats are conversations. Folders are the book.</p>
<h3>6. Privacy — decide this before you upload anything</h3>
<p>A memoir is almost never just about you. It’s about family, friends, exes, colleagues — real, living people, often captured in private letters and messages they never expected to see in print. This is where memoirists most often get into trouble, and it’s easy to get right if you decide the rules on day one:</p>
<ul>
<li><strong>The two-folder rule (from §4):</strong> raw exports live in <code>00_PRIVATE-ORIGINALS</code> and never touch any AI or cloud tool. Only reviewed copies enter the working archive.</li>
<li><strong>Triage everything sensitive into three buckets.</strong> <em>Green</em> — safe to work with as-is (your own journals, public material, harmless logistics). <em>Yellow</em> — fine after stripping phone numbers, addresses, and third-party identifying details. <em>Red</em> — genuinely private material about <em>other people</em>: someone’s illness, a family secret, a painful exchange, anything legally sensitive. For red material, don’t upload the raw thing at all — read it yourself and dictate a short summary plus the handful of lines that actually matter, and let only that summary into the archive.</li>
<li><strong>Check your AI tool’s privacy settings</strong> before the first upload, and set data-sharing / training options to whatever you’re comfortable with.</li>
<li><strong>Storing someone’s messages and quoting them are different questions.</strong> Anything you might want to quote from a private exchange will eventually need that person’s permission, or careful paraphrase. Don’t solve it now — just tag such material <code>[PERMISSION NEEDED]</code> as you go, so it’s findable later (§21).</li>
</ul>
<p>Set these rules once and they run quietly in the background for the whole project.</p>
<hr>
<h2>Part III — Gathering the material (Weeks 1–4)</h2>
<p>The goal here is narrow: get everything into <code>10_INBOX</code> in a form a computer can read — text, PDF, or transcribed audio. Rough is fine. Easiest sources first, so momentum builds.</p>
<h3>7. The easy wins</h3>
<ol>
<li><strong>Existing drafts, journals, notes.</strong> Copy them all into the inbox. Don’t reread, don’t fix, don’t judge. In they go.</li>
<li><strong>Documents, clippings, photos.</strong> PDFs and images go straight in. For anything online, save it as a PDF from the browser. Keep a <code>links.txt</code> file where you paste URLs you haven’t saved yet.</li>
<li><strong>Anything you’ve already made public — this is easy to forget and unusually valuable.</strong> Blog posts, social media threads, letters, a wedding speech, an interview, a talk. This material already exists <em>in your voice, with feeling in it</em> — it’s the single best existing source for Layer 2 and for the voice guide (§15). List everything you can remember; AI can help you track down transcripts and recordings of the public ones.</li>
</ol>
<h3>8. Text and chat messages</h3>
<p>Most messaging apps let you export a conversation as a plain-text file. On WhatsApp, for example: open the chat → tap the name at the top → <strong>Export Chat</strong> → <strong>Without Media</strong> (text is what matters; media can follow later for the few threads where it does). Other apps have an equivalent; a quick search for “export chat [app name]” will find it.</p>
<p>Send the exported file to yourself, drop it in <code>00_PRIVATE-ORIGINALS</code>, apply the triage from §6, and move the green/yellow copies into the inbox.</p>
<p>Start with the ten or fifteen threads that actually carry the story — the people at the center of it. You don’t need your entire message history. You need the conversations where the book happened.</p>
<h3>9. Email</h3>
<p>Three options, increasing in effort — the first is enough for most people:</p>
<ol>
<li><strong>Selective save-as-PDF (recommended start).</strong> Search your inbox by person, topic, or date range. For each important thread: open it → Print → Save as PDF → into <code>00_PRIVATE-ORIGINALS</code>, then triage. An afternoon of this on your twenty most important threads beats a full export you’ll never open.</li>
<li><strong>Connect email to your AI tool</strong> (many now support this). Useful for <em>discovery</em> — “find my correspondence with [person] from that year and summarize each thread.” Use it to find things, then save the threads that matter as PDFs so they live in the archive permanently.</li>
<li><strong>A full mailbox export</strong> produces a bulky technical file. Only worth it later, and only with a technically-minded helper. Skip for now.</li>
</ol>
<h3>10. Recordings — everything becomes a transcript</h3>
<p>The archive works in text, so every recording — interviews, voice notes, old videos, talks — needs transcribing:</p>
<ul>
<li><strong>Anything public with existing captions or transcripts</strong> (podcasts, videos, talks) can often be pulled directly — hand your AI the links and ask it to fetch and clean them up.</li>
<li><strong>Your own audio and video files:</strong> use a transcription app. Several excellent ones run <em>entirely on your own computer</em> so nothing gets uploaded — drag the file in, transcript comes out. Save results to <code>20_ARCHIVE/transcripts/</code>.</li>
<li><strong>For the two or three most important recordings</strong>, consider paying a human transcription service — worth it where every word might end up quoted.</li>
</ul>
<p>Label each transcript with date, occasion, and language.</p>
<h3>11. The catalogue — AI’s first big job</h3>
<p>Once the inbox has real volume — don’t wait for completeness; 70% is plenty — give your AI its first major task, inside your book workspace:</p>
<blockquote>
<p>“Go through everything in <code>10_INBOX</code>. For every file, create one line in a catalogue: filename, type, date or date range it covers, people mentioned, a two-sentence summary, and which archive subfolder it belongs in. Save the catalogue as <code>40_BOOK-BIBLE/catalogue.md</code>. Then tell me which files you couldn’t read or date, and ask me anything you couldn’t figure out.”</p>
</blockquote>
<p>Answer its questions, let it file everything into <code>20_ARCHIVE</code>, and spot-check a dozen entries yourself. From here on, the mess isn’t a mess — it’s a searchable library. This one step is where most of the “I don’t even know where to start” feeling dies.</p>
<hr>
<h2>Part IV — The Archive work: building the book’s skeleton (Weeks 3–8, AI-led)</h2>
<p>These are living documents, saved in <code>40_BOOK-BIBLE</code> and loaded into your book workspace. AI drafts them; you correct them. Each keeps growing for the life of the project.</p>
<h3>12. The master timeline</h3>
<p>The spine of everything. Ask your AI to build, from the entire archive, a chronological timeline: date, event, source file(s), people involved, one-line description — from the earliest relevant moment to wherever you decide the book ends. It will run to hundreds of entries. That’s correct: the book will use perhaps sixty of them, but you want to <em>choose from abundance</em>, and the timeline later becomes your fact-checking backbone (§21).</p>
<p>Then ask for a second pass on the same timeline: <strong>“mark the 25 moments with the highest emotional or narrative weight.”</strong> You’ll rewrite its list — half its guesses will be wrong, and your corrections (“no, the real moment that year was a conversation that isn’t in any file”) are themselves priceless Layer 2 material. Add the missing moments by hand. The moments that appear in <em>no document</em> are very often the heart of the book.</p>
<h3>13. Three more indexes</h3>
<ul>
<li><strong>People index:</strong> everyone who appears — with their role, first appearance, and where they show up in the archive. Later this doubles as your permissions checklist.</li>
<li><strong>Scenes list:</strong> moments that could become <em>scenes</em> — a specific room, a specific day, a single conversation. Books are built from scenes, not summaries. (“I struggled with the decision for months” is a summary; the night you finally decided is a scene.)</li>
<li><strong>Gap map:</strong> ask your AI, “based on the timeline, where are the holes? Which periods have almost no material? Which important moments have no notes?” The gap map becomes the agenda for your memory sessions.</li>
</ul>
<hr>
<h2>Part V — The Memory work: getting <em>you</em> onto the page (ongoing — the heart of the book)</h2>
<h3>14. Why your archive feels dry, and the method that fixes it</h3>
<p>Your files are dry because when you were living your life you were <em>living it</em>, not documenting your inner state. The feelings were real; they just never got written down. They are retrievable — and the reliable way to retrieve them is <strong>not</strong> “sit down and write about your feelings” (which produces either nothing or something stiff). It is <strong>being interviewed, out loud, anchored to specifics.</strong></p>
<p>Three formats, in order of importance:</p>
<p><strong>A. Walk-the-timeline sessions (the core practice).</strong> Twice a week, 60–90 minutes, actually blocked on your calendar. Open your book workspace, pick a stretch of the timeline, and say:</p>
<blockquote>
<p>“Interviewer mode. Here’s the period we’re covering: [event / stretch of time]. You have the timeline and the archive. Ask me one question at a time. Push past the version I’ve told people a hundred times. Ask about the physical and the specific: the room, the drive home, what the other person actually said, what I <em>didn’t</em> say. Follow up before moving on. Don’t summarize me back to myself, and don’t comfort me — just ask the next question.”</p>
</blockquote>
<p><strong>Record the session on your phone while you talk</strong> (you can also type or dictate answers into the AI — but the audio catches everything, including <em>how</em> you say things). Transcribe it (§10) into <code>30_MEMORY</code>.</p>
<p>That “push past the practiced version” instruction matters. Everyone has a handful of polished, three-minute answers about the big events of their life — the version you give at dinner parties. The book needs what’s <em>underneath</em> that version. An interviewer who has read your whole archive and can gently say “that’s the dinner-party answer — what actually happened?” is how you get there. And AI has one genuinely strange advantage over any human interviewer here: you cannot bore it, you cannot burden it, there’s nothing you need to protect it from, and 2 a.m. is fine.</p>
<p><strong>B. Voice memos in the wild.</strong> Memory doesn’t keep office hours. When something surfaces — driving, walking, cooking, half-asleep — talk into your phone for two minutes. No structure, no quality bar. Once a week, transcribe the batch into <code>30_MEMORY</code>. Six months of this becomes hundreds of fragments in your true voice, and a large share of the book’s best lines will come from here.</p>
<p><strong>C. Facts + feelings pairs.</strong> For each of your ~25 key moments (§12), the goal is a matched pair: a <em>facts card</em> (AI compiles it from the archive — date, who, what, sources) and a <em>feelings note</em> (a page of <em>your own transcribed words</em> about that moment, drawn from formats A and B). A chapter is ready to draft only when its moments have <em>both halves</em>. This is the concrete, checkable answer to “how do I get my personal story in”: <strong>a moment with no feelings note doesn’t go in the book yet.</strong></p>
<p>A word on the hard sessions. Most memoirs exist because something in the writer’s life was big enough to be worth a book — loss, illness, rupture, hardship, a hard-won change. Which means some sessions will cost you something. Plan for that like an adult instead of being ambushed by it: schedule the heavy ones when you have support around you afterward, not right before you need to function; give yourself permission to stop a session in the middle; and if the material is genuinely difficult, consider keeping a therapist or a trusted person in the loop while you’re in the thick of it. Many memoirists of hard material do exactly this. The book comes out <em>deeper</em> for it, not softer. No deadline outranks this.</p>
<h3>15. The voice guide and the verbatim vault</h3>
<p>Two more living documents for <code>40_BOOK-BIBLE</code>:</p>
<ul>
<li><strong>The voice guide.</strong> Ask your AI to study everything you’ve written and said — drafts, public posts, interview transcripts — and describe <em>how you actually talk and write</em>: sentence rhythm, the jokes you make, whether you run long or clipped, the words you’d never use. Have it give you ten sentences that sound like you and ten that don’t, with reasons. Then <em>you</em> edit its analysis. From then on the voice guide sits in your workspace and governs every drafted sentence, under one standing instruction: <em>when in doubt, plainer.</em></li>
<li><strong>The verbatim vault.</strong> A file of your best lines <em>exactly as you said them</em> — pulled from your notes, sessions, and public material. The test of a vault line is that no one else could have written it: it has your specific cadence, your specific noticing, a turn only you would take. Vault lines go into chapters <strong>untouched</strong>, and AI’s standing instruction is: never paraphrase a vault line. These are the sentences readers will remember, and they are, by definition, the ones AI could never have produced.</li>
</ul>
<hr>
<h2>Part VI — Shaping and drafting the book</h2>
<h3>16. First, decide what the book is (a human decision)</h3>
<p>Before chapter one, spend real time — ideally with an editor or a couple of book-literate friends — on questions no tool can answer:</p>
<ul>
<li><strong>What is this book about, in one sentence?</strong> A childhood in a particular place; surviving an illness; two countries and never quite belonging to either; a marriage and its end; caring for a dying parent; the cost of a career; recovery. Your life touches several of these — but <em>one</em> is the spine, and choosing it determines every cut. A memoir is not “everything that happened to me”; it’s one true thing, told through a life.</li>
<li><strong>Where does it end?</strong> Memoirs live or die on the ending. Not the last event chronologically — the last event <em>meaningfully</em>. Decide it early; it changes what the whole book is reaching toward.</li>
<li><strong>What stays out?</strong> Some things you’ll keep private, for yourself or for the people in them. Decide this deliberately, not by avoidance. Keep a short file, <code>not-in-the-book.md</code> — what’s on it is nobody’s business, but the list should exist.</li>
<li><strong>Who is it for?</strong> A stranger who shares your experience, or one who knows nothing about it? The answer shifts the balance between <em>explaining</em> and <em>remembering</em>.</li>
</ul>
<p>Ask your AI to argue <em>three different versions</em> of the book, each with a rough chapter arc — treat it as a sparring partner. But you choose. This choice <em>is</em> authorship.</p>
<h3>17. The chapter map and the chapter packet</h3>
<p>With the spine chosen, build the chapter map: 15–25 chapters, each with a working title, the period it covers, the two-to-four scenes it’s built on, and what it does for the whole. Then chapters get drafted <strong>one at a time</strong> — never “write me the book.” Each starts with AI assembling a <strong>chapter packet</strong>:</p>
<blockquote>
<p>“Assemble the packet for Chapter 7 [event / period]. From the archive: the facts card for each scene, relevant timeline entries, and key quotes from documents with their sources. From <code>30_MEMORY</code>: everything I’ve said about these moments, quoted exactly. From the vault: candidate lines. Then list what’s thin — where we need another memory session before drafting.”</p>
</blockquote>
<p>If the packet comes back thin on Layer 2, you don’t draft — you do a memory session on that gap first. This loop — packet → gap → session → packet — is the engine of the whole book.</p>
<h3>18. The drafting pipeline</h3>
<p>Five steps per chapter:</p>
<ol>
<li><strong>AI assembles a first draft from the packet</strong>, with instructions like: <em>“Write in my voice per the voice guide. Use only material in the packet — no invented details, dialogue, or feelings, ever. Where you’d need something we don’t have, leave a marked gap <code>[MISSING: …]</code>. Prefer my exact phrasing from the memory transcripts; use vault lines verbatim. Scenes, not summary. Plain over lyrical.”</em> The honest way to think about this draft: it is <em>dictation, arranged</em> — not writing. The words are already yours; the machine put them in order.</li>
<li><strong>Your pass, out loud.</strong> Print it or read it aloud. Mark three things: <em>wrong</em> (fix it), <em>not-me</em> (rephrase it in your words — often just by talking the correction into your recorder), and <em>missing</em> (the detail or feeling the draft danced around — usually the chapter’s real center; go get it in a session).</li>
<li><strong>AI revision</strong> from your marked-up pass. Repeat 2–3 until it’s honest. Then stop — polishing past <em>honest</em> makes it worse, not better.</li>
<li><strong>A human editor’s pass</strong> (§20) for structure, pacing, and cuts. A good editor’s greatest gift is deletion.</li>
<li><strong>A fact-check pass</strong> (§21) before the chapter is called done.</li>
</ol>
<p>Draft chapters in whatever order is workable — there’s no law requiring you to <em>write</em> chronologically, only to let the reader <em>read</em> that way. Many writers save the hardest chapters for last, when the craft muscles are strong.</p>
<h3>19. The anti-slop rules (load this list into your workspace)</h3>
<ol>
<li><strong>Nothing invented, ever.</strong> No detail, quote, scene, weather, or feeling that isn’t in the archive or a memory transcript. A marked gap is always better than a plausible fabrication — this is a <em>true story about real people</em>, and a single invented detail, once noticed, poisons the reader’s trust in the whole book.</li>
<li><strong>Your words are the raw material.</strong> AI arranges, tightens, and bridges; it does not originate emotional content.</li>
<li><strong>Vault lines are untouchable.</strong></li>
<li><strong>The cliché ban:</strong> <em>journey</em> (twice in the entire book, maximum), <em>rollercoaster of emotions</em>, <em>little did I know</em>, <em>a testament to</em>, <em>in that moment</em>, <em>tapestry</em>, <em>newfound</em>, <em>whirlwind</em>, opening a chapter with a dictionary definition, and tidy redemptive endings on chapters that don’t have one. Real life isn’t tidy; the prose shouldn’t pretend otherwise.</li>
<li><strong>The specificity test:</strong> every scene needs at least one detail <em>only you</em> could know.</li>
<li><strong>The read-aloud test:</strong> if a sentence doesn’t sound like you saying it, it goes.</li>
<li><strong>Restraint over intensity.</strong> Powerful material doesn’t need help — it needs room. When in doubt, <em>understate</em>. The strongest sentence about the hardest day is usually the plainest one.</li>
</ol>
<hr>
<h2>Part VII — The humans you’ll need</h2>
<h3>20. Ghostwriter, editor, or yourself — the honest options</h3>
<p><strong>Option A — You + AI + a freelance editor.</strong> You do the memory work and the drafting pipeline; you hire an experienced memoir editor for a developmental edit (structure, pacing) on the full manuscript, plus a professional copyedit at the end. Lowest cost — very roughly $5,000–20,000 in editing — most of your time, and the book that is most fully <em>yours</em>.</p>
<p><strong>Option B — A professional ghostwriter or collaborator leads.</strong> They run the interviews (replacing or supplementing §14A), draft, and shape; memoirs frequently carry a “with [name]” credit, which readers respect. Traditionally this runs $30,000–150,000+ and a year of their time — but here’s what changes with the method in this guide: <strong>a ghostwriter who walks into a finished archive, a built timeline, and fifty hours of memory transcripts works dramatically faster and better than one starting from a shoebox.</strong> Nothing in Parts II–V is wasted under any option. If a publisher acquires the book on a proposal, they may fund or arrange the collaborator.</p>
<p><strong>Option C — the hybrid, and the one I’d recommend: don’t decide yet.</strong> Do the setup, the archive, and two months of memory work. Then draft two or three <em>mid-intensity</em> chapters through the full pipeline. Now decide from <em>evidence</em>: if the drafting felt alive and the results read true, continue as Option A. If it felt like homework, you now hold the perfect package to hand a ghostwriter — and you’ll hire a better one, for less, because you know exactly what you’re asking for. Either way, interview any editor or ghostwriter partly <em>on your own material</em>: give them one chapter packet and ask how they’d approach it. How they talk about your voice tells you everything.</p>
<p>Whatever the path, one person holds <strong>veto power over every page</strong>: you.</p>
<h3>21. Fact-checking, permissions, and legal</h3>
<ul>
<li><strong>Fact-check with AI, verify with humans.</strong> Chapter by chapter: “check every date, name, title, number, and quoted document in this chapter against the archive and timeline; list every claim you cannot source.” Anything unsourced gets sourced, softened (“as I remember it”), or cut. Memory is unreliable in specific, well-documented ways — this pass catches the confident-but-wrong details before a reader does.</li>
<li><strong>Permissions.</strong> Work through the people index: private messages you quote need consent or paraphrase; people who appear in a painful light deserve, at minimum, a heads-up, and sometimes a veto over their own scenes. Your <code>[PERMISSION NEEDED]</code> tags from §6 become a simple checklist here. This is not just courtesy — it’s how you avoid both lawsuits and the quieter cost of rupturing a real relationship for a paragraph.</li>
<li><strong>A legal read</strong> by a media or publishing lawyer (defamation, privacy, quoted correspondence) is standard for any memoir that names real, living people — especially where the portrayal is unflattering. A traditional publisher usually arranges it; if you self-publish, arrange it yourself. It’s cheaper than the alternative.</li>
</ul>
<h3>22. Family and first readers</h3>
<p>The people closest to you will appear on many of these pages. Decide together, early, how they want to be involved — some want to read everything as it’s written, some want to read nothing until it’s done, some want their own scenes told only in <em>their</em> words (you can run the §14 interview process with them too, if they’re willing — their transcripts go in <code>30_MEMORY</code> alongside yours). And keep two or three trusted first readers — book-literate people who’ll tell you the truth — for the full manuscript. Not a committee. Two or three.</p>
<hr>
<h2>Part VIII — Rhythm and a realistic schedule</h2>
<h3>23. The weekly rhythm</h3>
<p>Books get finished by small, consistent effort, not heroic bursts. A sustainable week:</p>
<ul>
<li><strong>Two memory sessions</strong> (60–90 min each) — the non-negotiable core.</li>
<li><strong>One archive/admin block</strong> (60 min): transcribe the week’s voice memos, file new material, update the timeline and catalogue with your AI.</li>
<li><strong>One drafting block</strong> (2–3 hrs, once drafting starts): one chapter loop — a packet, or a draft, or your read-aloud pass.</li>
</ul>
<p>Roughly five to six focused hours a week. Protect the memory sessions above all else; everything else can slip a week without harm.</p>
<h3>24. The arc of the project</h3>
<ul>
<li><strong>Month 1:</strong> setup, privacy rules, gathering, first catalogue. <em>Milestone: the mess is a library.</em></li>
<li><strong>Months 2–3:</strong> timeline and indexes; memory sessions begin; voice guide v1. <em>Milestone: the 25 key moments identified, sessions running.</em></li>
<li><strong>Months 3–6:</strong> memory work deepens; the book-spine decision (§16); chapter map; the first two or three pilot chapters; <strong>the decision point on ghostwriter vs. self (§20C).</strong></li>
<li><strong>Months 6–12:</strong> chapter production, one loop at a time; permissions begin in parallel.</li>
<li><strong>Months 12–18:</strong> full-manuscript edit, fact-check, permissions closed, legal read, and the final read-aloud pass — yours.</li>
</ul>
<p>Twelve to eighteen months to a real manuscript is <em>normal and good</em> for a serious memoir. Faster is possible; it is rarely better. And note what exists by month three regardless of what happens with publishers: a complete, organized, verified archive of your life’s material, and hours of your own testimony in your own voice. For your family, and for the record, that alone justifies the work. The book is built on top of something that already matters.</p>
<hr>
<h2>Appendix A — Prompt library (copy-paste starters)</h2>
<p><strong>Cataloguing:</strong> <em>“Go through <code>10_INBOX</code>. For each file: filename, type, date range, people, two-sentence summary, target archive folder. Save as <code>40_BOOK-BIBLE/catalogue.md</code>. List unreadable or undatable files and ask me what you couldn’t figure out.”</em></p>
<p><strong>Timeline:</strong> <em>“From everything in <code>20_ARCHIVE</code>, build a chronological timeline: date | event | people | source files | one line. Save as <code>40_BOOK-BIBLE/timeline.md</code>. Then mark the 25 entries highest in emotional or narrative weight, and separately list any periods with suspiciously little material.”</em></p>
<p><strong>Interviewer mode:</strong> <em>“Interviewer mode for [period / event]. One question at a time, follow-ups before moving on. Push past my practiced version. Ask physical and specific. Don’t summarize me, don’t comfort me.”</em></p>
<p><strong>Voice guide:</strong> <em>“Study everything I’ve written and said in the archive. Describe my voice: rhythm, vocabulary, humor, what I never do. Give 10 sentences that sound like me and 10 that don’t, with reasons. Save as <code>40_BOOK-BIBLE/voice-guide.md</code> for me to edit.”</em></p>
<p><strong>Chapter packet:</strong> <em>“Assemble the packet for Chapter [N]: facts cards per scene with sources; every relevant memory-transcript passage, quoted exactly; candidate vault lines; then list where the material is thin and what to cover in a memory session before drafting.”</em></p>
<p><strong>Chapter draft:</strong> <em>“Draft Chapter [N] from its packet only. My voice per the voice guide. No invented details, dialogue, or feelings — mark gaps as <code>[MISSING: …]</code>. Prefer my exact phrasing; vault lines verbatim. Scenes, not summary. Plain over lyrical. Obey the anti-slop rules.”</em></p>
<p><strong>Fact-check:</strong> <em>“Check every date, name, title, number, and quote in this chapter against the archive and timeline. Return a table: claim | source file | confirmed / conflict / unsourced.”</em></p>
<h2>Appendix B — Pre-upload privacy checklist</h2>
<p>Before any file moves from <code>00_PRIVATE-ORIGINALS</code> into the working archive, ask: Is anyone’s phone number, address, or contact detail in it? <em>(Strip it.)</em> Does it contain another person’s private pain or a family secret? <em>(Summarize it instead, or ask them first.)</em> Is it a private message you might want to quote? <em>(Tag <code>[PERMISSION NEEDED]</code>.)</em> Could it embarrass or expose someone who isn’t you? <em>(Handle deliberately, not by accident.)</em> When unsure — leave it in originals; a summary in the archive can always point back to it.</p>
<hr>
<p><em>One last thing. Your archive is dry because, when it mattered, you were busy living instead of writing it down. The record of the living exists. This method exists to add the one thing only you have: what it was actually like to be inside it. Organize with the machine. Remember out loud. Decide everything yourself. That’s the whole thing.</em></p>
</div>]]></content:encoded>
  </item>
  <item>
    <title>Blog now self-hosted</title>
    <link>https://slidemagic.com/blog/blog-now-self-hosted</link>
    <guid isPermaLink="true">https://slidemagic.com/blog/blog-now-self-hosted</guid>
    <pubDate>Mon, 06 Jul 2026 11:15:04 GMT</pubDate>
    <dc:creator>Jan Schultink</dc:creator>
    <description><![CDATA[For the first time in 18 years, the SlideMagic blog now runs on my own servers. We went from Blogger, to Squarespace, now to slidemagic.com. AI enabled me to quickly write a solution for hosting and editing the blog and manage the email and rss subscriptions. The big advantage is that I am no…]]></description>
    <content:encoded><![CDATA[<p>For the first time in 18 years, the SlideMagic blog now runs on my own servers. We went from Blogger, to Squarespace, now to <a href="http://slidemagic.com">slidemagic.com</a>. AI enabled me to quickly write a solution for hosting and editing the blog and manage the email and rss subscriptions. The big advantage is that I am no longer tied to formats and templates that always felt very forced, I can simply apply my own. Secondly, I can back through 18 years of post history and clean up broken links and images.</p>
<p>The current design of the blog is still very plain and standard, I will update it later. For the moment I made sure that the plumbing works. If you encounter any issues, let me know.</p>
]]></content:encoded>
  </item>
  <item>
    <title>Dream cycles</title>
    <link>https://slidemagic.com/blog/2026/5/4/dream-cycles</link>
    <guid isPermaLink="true">https://slidemagic.com/blog/2026/5/4/dream-cycles</guid>
    <pubDate>Mon, 04 May 2026 10:22:55 GMT</pubDate>
    <dc:creator>Jan Schultink</dc:creator>
    <category>AI</category>
    <category>Creativity</category>
    <description><![CDATA[Humans process information absorbed during the day in a good night’s sleep. Important things get put in long-term memory, details that are less important go to the “forget bin”. Stress and noise gets reduced. When we get up, we feel refreshed and ready to get going again. Memory is a big issue in…]]></description>
    <content:encoded><![CDATA[<p>Humans process information absorbed during the day in a good night’s sleep. Important things get put in long-term memory, details that are less important go to the “forget bin”. Stress and noise gets reduced. When we get up, we feel refreshed and ready to get going again.</p>
<p>Memory is a big issue in AI at the moment. A few months ago, it was about remembering your last 3 prompts (sentences). Today, these “context windows” can span novels, to the point where this memory actually starts to confuse the model. A technical solution: dream cycles where the AI model peruses its information, selectively forgets details, and stores important data for future reference.</p>
<p>When it comes to presentation design, it is important to give your thoughts rest as well. Coming back to a story line after a few days makes your realize what actually is the best way to communicate the message.</p>
<p>And a fresh pair of AI eyes can help as well. Clear the context of your model, or open an entirely different one, upload your draft and ask whether this is actually the best way to tell your story…</p>
]]></content:encoded>
  </item>
  <item>
    <title>ChatGPT Images 2 beats Nano Banana</title>
    <link>https://slidemagic.com/blog/2026/4/26/chatgpt-images-2-beats-nano-banana</link>
    <guid isPermaLink="true">https://slidemagic.com/blog/2026/4/26/chatgpt-images-2-beats-nano-banana</guid>
    <pubDate>Sun, 26 Apr 2026 03:43:01 GMT</pubDate>
    <dc:creator>Jan Schultink</dc:creator>
    <category>AI</category>
    <category>Images</category>
    <category>Software</category>
    <description><![CDATA[Another day, another model improvement. The latest visual model by OpenAI is now the gold standard for creating realistic image, beating Google’s Nano Banana (August 2025). I prompted a “911 in Hoogeveen” back in an earlier post to Nano Banana (left), and the ChatGPT result today to the right. Nano…]]></description>
    <content:encoded><![CDATA[<p>Another day, another model improvement. The latest visual model by OpenAI is now the gold standard for creating realistic image, beating Google’s Nano Banana (August 2025).</p>
<p>I prompted a “911 in Hoogeveen” back in an <a href="https://slidemagic.com/blog/2025/8/30/nano-banana">earlier post t</a>o Nano Banana (left), and the ChatGPT result today to the right. Nano Banana figured out Hoogeveen was a town in the Netherlands, and created a historical Dutch town as the backdrop, ChatGPT got the actual details of the town (which I recognize very well), but created its own mashup version of the city.</p>
<p><img src="https://d1oneoqxddswon.cloudfront.net/chatgpt-images-2-beats-nano-banana/figure-1.webp" alt=""></p>
<p>Text rendering is now great. Look at the traffic sign: correct spelling and places relevant to the town. The model is actually incredibly good at making slide in consistent on-brand format. Below the result of a request to transform a slide in a 1960s Swiss graphic design style. The catch: you get pixels not a file you can edit…</p>
<p><img src="https://d1oneoqxddswon.cloudfront.net/chatgpt-images-2-beats-nano-banana/figure-2.webp" alt=""></p>
<p>It achieves these results not by just being a better pixel generation model. The response to a prompt now involves reasoning about it, sketching a few raw options, ‘seeing’ (an LLM cannot see) the intermediary results, picking the best one, then producing the final result in pixels.</p>
<p>ChatGPT Images 2 is now the default model in ChatGPT, it will be used when you ask it to create an image. Set the model effort to ‘thinking’ to add more reasoning effort in the processing.</p>
<p>To be continued.</p>
]]></content:encoded>
  </item>
  <item>
    <title>Codex Computer Use - control any app on your machine</title>
    <link>https://slidemagic.com/blog/2026/4/24/codex-computer-use-control-any-app-on-your-machine</link>
    <guid isPermaLink="true">https://slidemagic.com/blog/2026/4/24/codex-computer-use-control-any-app-on-your-machine</guid>
    <pubDate>Fri, 24 Apr 2026 04:19:48 GMT</pubDate>
    <dc:creator>Jan Schultink</dc:creator>
    <category>AI</category>
    <category>Software</category>
    <category>SlideMagic</category>
    <description><![CDATA[Another day, another presentation AI tool. Codex Computer Use is a plugin for OpenAI’s Codex desktop app. It enables control of any app on your machine using the regular human interface: ‘seeing’ screen and making clicks. (Mac only, and not available in the EU/UK because of regulatory…]]></description>
    <content:encoded><![CDATA[<p>Another day, another presentation AI tool. <a href="https://developers.openai.com/codex/app/computer-use">Codex Computer Use</a> is a plugin for OpenAI’s Codex desktop app. It enables control of any app on your machine using the regular human interface: ‘seeing’ screen and making clicks. (Mac only, and not available in the EU/UK because of regulatory restrictions).</p>
<p>Its powers are phenomenal. SlideMagic is a quirky app with a small user base. In a few minutes I got it to insert a profit and loss table, add a year to it, and then take the last year of the table and turn that into a horizontal waterfall chart.</p>
<p>In PowerPoint for example, this tool will be much more useful than the Claude PowerPoint plugin, which “fights” complex PPTX file formats (a huge amount of nexted XML tags) to make simple edits like moving a box. The Codex Computer Use plugin can simple drag the box.</p>
<p>This feature is extremely token-hungry though, probably because of the screenshot data that gets send back to the server.</p>
]]></content:encoded>
  </item>
  <item>
    <title>Claude Design is here, what does it mean for presentations?</title>
    <link>https://slidemagic.com/blog/2026/4/18/claude-design-is-here</link>
    <guid isPermaLink="true">https://slidemagic.com/blog/2026/4/18/claude-design-is-here</guid>
    <pubDate>Sat, 18 Apr 2026 05:32:03 GMT</pubDate>
    <dc:creator>Jan Schultink</dc:creator>
    <description><![CDATA[I was waiting for this announcement, and Anthropic did announce a few hours ago: Claude Design. There are many demo and review videos online that show the features, I will focus on a few specific issues. <div class="video-embed"…]]></description>
    <content:encoded><![CDATA[<p>I was waiting for this announcement, and Anthropic did announce a few hours ago: <a href="https://www.anthropic.com/news/claude-design-anthropic-labs">Claude Design</a>. There are many demo and review videos online that show the features, I will focus on a few specific issues.</p>
<div class="video-embed" style="position:relative;padding-bottom:56.25%;height:0;overflow:hidden;margin:1.5rem 0"><iframe src="https://www.youtube.com/embed/t_LBECIQQqs" loading="lazy" allowfullscreen frameborder="0" style="position:absolute;top:0;left:0;width:100%;height:100%"></iframe></div>
<p>The big issue for enterprises when it comes to presentations and documents is to keep all employees “on brand”. The designer of the corporate web site gets it right, but what about the new analyst who works late at night to prepare the quarterly revenue update presentation? Claude Design does a great job here to capture fonts, colors, and style guidelines in one place.</p>
<p>For enterprise AI workflows and systems, context is everything. And the Claude set up makes it easy to access files, information, data, anything.</p>
<p>The current Claude Design application is a web app, that has not been integrated in the desktop all yet (it will probably happen soon). For presentations, its a wrapper around Claude’s ability to manipulate and create slides. At the moment, Claude Design treats presentation slides as HTML. (Unlike Claude Code/Cowork that can work directly with PPTX). As you interact with Claude Design your presentation comes out beautifully, but will have a “web site” look and feel. (Maybe that is actually a better feel than corporate PowerPoint?). Your presentation is HTML with a 16:9 aspect ratio without the resizing options.</p>
<p>When you are done, you can export to many formats, of which PPTX is one. Once exported, Claude Design can no longer edit the resulting PPTX file. (Obviously you can ask Claude Code/Cowork to take over from there, but that app will miss the context that you created before).</p>
<p>The underlying design engine of Claude does not seem to have changed. Running a few tests, I still see the same things it is really good at, and the ones it really struggles with.</p>
<p>We are getting close to where AI can handle design of presentations. What has not been solved (yet), is the workflow of tweaking/updating/modifying decks among multiple people, where enterprises have the culture baked in of making edits to a shared document in a 1990s file format that gets emailed around between junior staff, senior managers, and everyone in between.</p>
<p>But that could change as well. The way people write code has more or less changed overnight sometime mid January 2026, maybe the same will happen to presentation creation sometime this year.</p>
]]></content:encoded>
  </item>
  <item>
    <title>None of the tools were right, so I quickly wrote one...</title>
    <link>https://slidemagic.com/blog/2026/2/25/none-of-the-tools-were-right-so-i-quickly-wrote-one</link>
    <guid isPermaLink="true">https://slidemagic.com/blog/2026/2/25/none-of-the-tools-were-right-so-i-quickly-wrote-one</guid>
    <pubDate>Wed, 25 Feb 2026 06:23:21 GMT</pubDate>
    <dc:creator>Jan Schultink</dc:creator>
    <category>Software</category>
    <description><![CDATA[This is 2026… I needed a super basic text editor for Google Drive. If you double click a text file in Google Drive, it will convert it to a bloated Google Doc for you. You can install text editor apps, but they all come with a catch: too many features, 1990s UI design, ads, paid plans. So i used…]]></description>
    <content:encoded><![CDATA[<p>This is 2026… I needed a super basic text editor for Google Drive. If you double click a text file in Google Drive, it will convert it to a bloated Google Doc for you. You can install text editor apps, but they all come with a catch: too many features, 1990s UI design, ads, paid plans. So i used Codex to write me one… Writing the app took 10 minutes, configuring the Google Cloud Console a few hours (but now I know the drill).</p>
<p><img src="https://d1oneoqxddswon.cloudfront.net/none-of-the-tools-were-right-so-i-quickly-wrote-one/figure-1.webp" alt=""></p>
<p>I have requested Google to approve it to get rid of warnings when you install it. The primary user is me anyway, so I won’t put it out in the add-on market place.</p>
<p>You can try it: <a href="https://drivedraft.slidemagic.com">drivedraft.slidemagic.com</a>. Sign in with your Google Account. Now go to Google Drive and right-click a .txt or .md file and choose ‘Open With’ DriveDraft.</p>
]]></content:encoded>
  </item>
  <item>
    <title>PowerPoint via Whatsapp</title>
    <link>https://slidemagic.com/blog/2026/2/17/powerpoint-via-whatsapp</link>
    <guid isPermaLink="true">https://slidemagic.com/blog/2026/2/17/powerpoint-via-whatsapp</guid>
    <pubDate>Tue, 17 Feb 2026 06:54:50 GMT</pubDate>
    <dc:creator>Jan Schultink</dc:creator>
    <category>AI</category>
    <category>Software</category>
    <description><![CDATA[I have been experimenting with OpenClaw, a 24/7 personal AI assistant. It is an open source project that was created over the past month, created almost by accident as a hobby project by a developer. Late last year, developers discovered that using an AI coding tool for non-coding applications…]]></description>
    <content:encoded><![CDATA[<p>I have been experimenting with <a href="https://openclaw.ai">OpenClaw</a>, a 24/7 personal AI assistant. It is an open source project that was created over the past month, created almost by accident as a hobby project by a developer. Late last year, developers discovered that using an AI coding tool for non-coding applications really works, especially if you can give it access to local files (rather than chatting). Next step: keep the AI agent running 24/7. Next step, find a way to let the AI agent keep some context about you. (Context memory is a big issue in AI, it fills up at some time, so storing bits of context for future reference enables persistent awareness). Next step, implement recurring instructions. Next, make the AI assistant available from any channel, including Whatsapp. This, combined with full system access, creates an incredibly powerful AI assistant (that can also be incredibly destructive). “It’s 2AM, I have a 12 hour to do list and full shell access, lovin’ it”. What can possibly go wrong.</p>
<p>So it requires some technical knowledge to run this thing in a vaguely responsible way. I put it on AWS EC2 in a completely isolated virtual network, with an access tunnel that only I control, plus a number of prompt injection filters running on yet another server. (OpenClaw’s founder has joined OpenAI exactly for that reason, to get the financial resources to fix the complexity and security issues)</p>
<p>Working with it, enables me to get a feel for the future. Direct instructions to applications (code editors, presentation design software, spreadsheets, food takout apps) will become increasingly irrelevant.</p>
<p>We will move from well-designed, beautiful, easy to understand, visual user interfaces that humans can interact with directly to clear and transparent API endpoints that an agent can call on behalf of a human.</p>
<p>Interesting times.</p>
]]></content:encoded>
  </item>
  <item>
    <title>AI images are the new stock images</title>
    <link>https://slidemagic.com/blog/2026/2/16/ai-images-are-the-new-stock-images</link>
    <guid isPermaLink="true">https://slidemagic.com/blog/2026/2/16/ai-images-are-the-new-stock-images</guid>
    <pubDate>Mon, 16 Feb 2026 09:33:43 GMT</pubDate>
    <dc:creator>Jan Schultink</dc:creator>
    <category>AI</category>
    <category>Images</category>
    <description><![CDATA[People are starting to develop a pretty good sense of whether an image “smells like AI”. The audience will notice when you use them just as visual fillers like you used to use stock images. (“Life-style conscious gen-z person working from the local cafe”). Completely obvious AI renderings are…]]></description>
    <content:encoded><![CDATA[<p>People are starting to develop a pretty good sense of whether an image “smells like AI”. The audience will notice when you use them just as visual fillers like you used to use stock images. (“Life-style conscious gen-z person working from the local cafe”).</p>
<p><img src="https://d1oneoqxddswon.cloudfront.net/ai-images-are-the-new-stock-images/figure-1.webp" alt=""></p>
<p>Completely obvious AI renderings are comparable to clip art of the earlly 2000s. Hyper realistic AI images are similar to stock images, “something is off here”.</p>
<p>Apply the same approach to AI images as you did to stock images.</p>
]]></content:encoded>
  </item>
  <item>
    <title>"Files are so back"</title>
    <link>https://slidemagic.com/blog/2026/2/13/files-are-so-back</link>
    <guid isPermaLink="true">https://slidemagic.com/blog/2026/2/13/files-are-so-back</guid>
    <pubDate>Fri, 13 Feb 2026 14:32:34 GMT</pubDate>
    <dc:creator>Jan Schultink</dc:creator>
    <category>AI</category>
    <category>Software</category>
    <description><![CDATA[The past decade with spend a lot of energy moving all our files into the cloud, and accessing them through a browser-based application. That is going to reverse in the era of AI. A good old desktop folder is the perfect context for an AI agent. All information in one place. Different formats,…]]></description>
    <content:encoded><![CDATA[<p>The past decade with spend a lot of energy moving all our files into the cloud, and accessing them through a browser-based application. That is going to reverse in the era of AI.</p>
<p>A good old desktop folder is the perfect context for an AI agent. All information in one place. Different formats, different applications, all accessible and editable.</p>
<p>I started experimenting with a spreadsheet/presentation workflow that mirrors the way I write code. Pointing Claude Code at a directory with files and let it orchestrate analysis and design under my supervision.</p>
]]></content:encoded>
  </item>
  <item>
    <title>PowerPoint -&gt; rendering engine</title>
    <link>https://slidemagic.com/blog/2026/2/12/powerpoint-gt-rendering-engine</link>
    <guid isPermaLink="true">https://slidemagic.com/blog/2026/2/12/powerpoint-gt-rendering-engine</guid>
    <pubDate>Thu, 12 Feb 2026 11:47:54 GMT</pubDate>
    <dc:creator>Jan Schultink</dc:creator>
    <description><![CDATA[Programming languages have always been a necessary evil. A way to translate human intent into something a machine can execute. Strict syntax, rigid rules, brackets in the right place. Presentation software has had the same problem. You want to communicate an idea, but first you need to learn how to…]]></description>
    <content:encoded><![CDATA[<p>Programming languages have always been a necessary evil. A way to translate human intent into something a machine can execute. Strict syntax, rigid rules, brackets in the right place.</p>
<p>Presentation software has had the same problem. You want to communicate an idea, but first you need to learn how to manipulate shapes, align text boxes, format charts, pick colors, fiddle with layouts. The tool sits between you and your intent.</p>
<p>AI is changing this. You can now describe what you want in plain language, the way you would have briefed a graphic designer ten years ago. “Put the revenue chart on the left, key takeaway on the right, keep it clean.” The difference is that the result comes back in seconds, not days.</p>
<p>And here is the interesting bit: it does not really matter which application your AI assistant uses under the hood to build the slides. The end product is a flattened file, a PDF, an image. The mechanical production of the slides is becoming invisible.</p>
<p>PowerPoint is not going away, but its role is shifting. It is moving from being a user interface for a human designer to being a rendering engine for an AI. The way a browser renders HTML that no one writes by hand anymore.</p>
<p>We are going back to a more natural way of working. Talking to a person (or an AI) about what you want to say, and getting a visual result. The detour through complex software UI was a historical accident, not the destination</p>
]]></content:encoded>
  </item>
  <item>
    <title>The "wait for AI" workflow</title>
    <link>https://slidemagic.com/blog/2026/2/10/the-wait-for-ai-workflow</link>
    <guid isPermaLink="true">https://slidemagic.com/blog/2026/2/10/the-wait-for-ai-workflow</guid>
    <pubDate>Tue, 10 Feb 2026 10:32:54 GMT</pubDate>
    <dc:creator>Jan Schultink</dc:creator>
    <category>Creativity</category>
    <category>AI</category>
    <description><![CDATA[As AI gets more and more capable and I use it for more and more things in my daily workflow, it creates a new problem: waiting for AI. Most tasks now take 1-3 minutes for which you have to wait for the result. Most takes would have taken you much much more than that if you were to do them yourself,…]]></description>
    <content:encoded><![CDATA[<p>As AI gets more and more capable and I use it for more and more things in my daily workflow, it creates a new problem: waiting for AI. Most tasks now take 1-3 minutes for which you have to wait for the result. Most takes would have taken you much much more than that if you were to do them yourself, so a big productivity gain, but, 1-3 minutes is too short to go and do something else, so you wait, get distracted, break your flow, and find yourself getting back to what you were working on 30 minutes later. “Ah small mistake, let’s do fix that. Click. 1-3 minutes wait.</p>
<p>I have not found a solution yet, and am experimenting:</p>
<ul>
<li>Running lots of agents in parallel, so it is like a plate-on-stick catching game</li>
<li>Running the tasks in parallel of an activity that is easy to interrupt (watching a tutorial video)</li>
<li>Writing a quick blog post…</li>
<li>Etc.</li>
</ul>
<p>A new world</p>
]]></content:encoded>
  </item>
  <item>
    <title>Claude plug-in for PowerPoint</title>
    <link>https://slidemagic.com/blog/2026/2/9/claude-plug-in-for-powerpoint</link>
    <guid isPermaLink="true">https://slidemagic.com/blog/2026/2/9/claude-plug-in-for-powerpoint</guid>
    <pubDate>Mon, 09 Feb 2026 07:34:31 GMT</pubDate>
    <dc:creator>Jan Schultink</dc:creator>
    <category>AI</category>
    <category>PowerPoint</category>
    <description><![CDATA[This has gone under the radar screen for me. The Claude plugin for PowerPoint is available for Claude Max, Team, and Enterprise users. It links to your existing Claude account (to burn tokens) and does exactly what you expect it to do. More information here.]]></description>
    <content:encoded><![CDATA[<p>This has gone under the radar screen for me. The Claude plugin for PowerPoint is available for Claude Max, Team, and Enterprise users. It links to your existing Claude account (to burn tokens) and does exactly what you expect it to do. More information <a href="https://support.claude.com/en/articles/13521390-using-claude-in-powerpoint">here</a>.</p>
]]></content:encoded>
  </item>
  <item>
    <title>On the "danger" of AI</title>
    <link>https://slidemagic.com/blog/2026/2/9/on-the-danger-of-ai</link>
    <guid isPermaLink="true">https://slidemagic.com/blog/2026/2/9/on-the-danger-of-ai</guid>
    <pubDate>Mon, 09 Feb 2026 06:20:06 GMT</pubDate>
    <dc:creator>Jan Schultink</dc:creator>
    <category>AI</category>
    <description><![CDATA[Recently, people start getting really concerned about autonomous AI doing its thing with your passwords and credit cards. But I think that not that much has changed since the first emergence of computers. Computers trade billions in stocks and currencies, run nuclear powerpoint plants. The…]]></description>
    <content:encoded><![CDATA[<p>Recently, people start getting really concerned about autonomous AI doing its thing with your passwords and credit cards. But I think that not that much has changed since the first emergence of computers. Computers trade billions in stocks and currencies, run nuclear powerpoint plants.</p>
<p>The difference, these systems are carefully monitored and are predictable and well-understood. It is not about the intelligence of the software, it is about the level of control you give it. People wanting “<a href="https://openclaw.ai">to push the boundaries</a>” and see how far AI can go seem to be putting a 10 year with Microsoft Flight Simulator experience at the controls of a real 747.</p>
<p>I have started to use AI tools heavily in my day-to-day work. Not for email and calendar management, but for coding and document production. All seems reasonably under control, things being sandboxed on my own machine. “Reasonably” What is not, is the chaotic user interface when it comes to giving permissions to things on your file system. Many of these questions will not be understood by the IT layman.</p>
<p>Everyone is raving about Anthropic’s Cowork tool to automate knowledge work. Many incumbent database/information providers and consultancy firm’s stock prices get hammered. The real revolution for Anthropic might be an acquisition that did not get a lot of press. In December, <a href="https://bun.com/blog/bun-joins-anthropic">they acquired Bun</a>, a software development platform. My sense is that Anthropic is developing a trusted platform that can build and run code safely on your computer without the constant flow of questions whether it is OK to install package x, y, and z. I think AI models will become a commodity, the real winner in the next generation of computing will be the player that offers this trusted platform that can keep AI in check.</p>
<p>Let’s read this post in 2036 again and see what happened :-)</p>
]]></content:encoded>
  </item>
</channel>
</rss>