<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Fabian Krumbholz — Articles</title>
    <link>https://krumbholz.de/blog/</link>
    <description>Written explanations of what Fabian Krumbholz speaks about. Each article names the session it demonstrates.</description>
    <language>en-GB</language>
    <atom:link href="https://krumbholz.de/rss.xml" rel="self" type="application/rss+xml" />
    <lastBuildDate>Mon, 12 Oct 2026 12:00:00 GMT</lastBuildDate>
    <item>
      <title>How I build a hands-on workshop that people finish</title>
      <link>https://krumbholz.de/blog/building-a-workshop-people-finish/</link>
      <guid isPermaLink="true">https://krumbholz.de/blog/building-a-workshop-people-finish/</guid>
      <pubDate>Mon, 12 Oct 2026 12:00:00 GMT</pubDate>
      <description>&lt;p&gt;What I learned building hands-on workshops as a GDE: prepare and test everything, automate the boring parts, keep the room together, and leave time for the people in it.&lt;/p&gt;&lt;ul&gt;&lt;li&gt;A workshop is a start, not a finished product. People should leave with a working first version and the wish to continue at home.&lt;/li&gt;&lt;li&gt;Give people slides, a guide and a ready-made repo they keep. Say at the start that all of it stays online, so nobody takes notes or photos.&lt;/li&gt;&lt;li&gt;Spend the room&amp;apos;s time on tasks that teach and are fun. Script the setup, prepare everything else, and test it all yourself from an empty machine.&lt;/li&gt;&lt;li&gt;Keep the room together, and build the workshop so it runs without you. Then you have time for the people in it.&lt;/li&gt;&lt;/ul&gt;</description>
    </item>
  </channel>
</rss>
