<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet type="text/xsl" href="../assets/xml/rss.xsl" media="all"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Joep Schuurkes (Posts about conferences)</title><link>https://smallsheds.garden/</link><description></description><atom:link href="https://smallsheds.garden/categories/cat_conferences.xml" rel="self" type="application/rss+xml"></atom:link><language>en</language><copyright>Contents © 2026 &lt;a href="mailto:site@joep.slmail.me"&gt;Joep Schuurkes&lt;/a&gt; 
&lt;a href="https://creativecommons.org/licenses/by-sa/4.0/" rel="nofollow" target="_blank"&gt;
&lt;img alt="Creative Commons BY-SA License" style="border-width:0;margin: 0px 0px 4px 0px;" src="https://licensebuttons.net/l/by-sa/4.0/80x15.png" /&gt;
&lt;/a&gt;
</copyright><lastBuildDate>Sat, 04 Jul 2026 11:02:57 GMT</lastBuildDate><generator>Nikola (getnikola.com)</generator><docs>http://blogs.law.harvard.edu/tech/rss</docs><item><title>Notes from the March '24 FroGS conf open space</title><link>https://smallsheds.garden/blog/2024/notes-from-the-march-24-frogs-conf-open-space/</link><dc:creator>Joep Schuurkes</dc:creator><description>&lt;div&gt;&lt;p&gt;Yesterday &lt;a href="https://elizabethzagroba.com/"&gt;Elizabeth Zagroba&lt;/a&gt;, &lt;a href="https://www.huibschoots.nl/"&gt;Huib Schoots&lt;/a&gt;, &lt;a href="https://www.linkedin.com/in/techsannetized/"&gt;Sanne Visser&lt;/a&gt; and I ran another &lt;a href="https://frogsconf.nl"&gt;FroGS conf&lt;/a&gt; online open space. There were plenty of great sessions, below are some notes from the five sessions I participated in. Thank you to everyone who was there, I had a great time!&lt;/p&gt;
&lt;p&gt;If you want to join one of our next FroGS conf events, head over to &lt;a href="https://frogsconf.nl/"&gt;our site&lt;/a&gt; and &lt;a href="https://frogsconf.nl/register/"&gt;subscribe&lt;/a&gt; to our newsletter.&lt;/p&gt;
&lt;h2 class="small"&gt;From notes to shared documentation culture&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Co-creation works for code. In what ways is co-creation for documentation different?&lt;/li&gt;
&lt;li&gt;Why do we talk about "an audience" for documentation, instead of about "the contributors"?&lt;/li&gt;
&lt;li&gt;The purpose of documentation flips from "what we build" to "what we built".&lt;/li&gt;
&lt;li&gt;Old research paper on documentation: only documentation with lasting usefulness is architecture and test cases. Everything else is just notes.&lt;/li&gt;
&lt;li&gt;Documentation heuristic: Is it easier/faster to reverse engineer it instead?&lt;p&gt;&lt;a href="https://smallsheds.garden/blog/2024/notes-from-the-march-24-frogs-conf-open-space/"&gt;Read more…&lt;/a&gt; (2 min remaining to read)&lt;/p&gt;&lt;/li&gt;&lt;/ul&gt;&lt;/div&gt;</description><category>conferences</category><guid>https://smallsheds.garden/blog/2024/notes-from-the-march-24-frogs-conf-open-space/</guid><pubDate>Sat, 23 Mar 2024 23:00:00 GMT</pubDate></item><item><title>Two styles of leadership in spreading context-driven testing (TITANconf)</title><link>https://smallsheds.garden/blog/2015/two-styles-of-leadership-in-spreading-context-driven-testing-titanconf/</link><dc:creator>Joep Schuurkes</dc:creator><description>&lt;div&gt;&lt;p&gt;The last weekend of August I spent with some great people - Kristoffer Ankarberg (&lt;a href="https://twitter.com/KrisAnkarberg"&gt;@KrisAnkarberg&lt;/a&gt;), Kristoffer Nordström (&lt;a href="https://twitter.com/kristoffer_nord"&gt;@kristoffer_nord&lt;/a&gt;), Anna Brunell (&lt;a href="https://twitter.com/Anna_Brunell"&gt;@Anna_Brunell&lt;/a&gt;), Fredrik Thuresson (&lt;a href="https://twitter.com/Thure98"&gt;@Thure98&lt;/a&gt;), Maria Kedemo (&lt;a href="https://twitter.com/mariakedemo"&gt;@mariakedemo&lt;/a&gt;), Henrik Andersson (&lt;a href="https://twitter.com/henkeandersson"&gt;@henkeandersson&lt;/a&gt;), Maria Månsson, Amy Philips (&lt;a href="https://twitter.com/ItJustBroke"&gt;@ItJustBroke&lt;/a&gt;), Richard Bradshaw (&lt;a href="https://twitter.com/FriendlyTester"&gt;@FriendlyTester&lt;/a&gt;), Duncan Nisbet (&lt;a href="https://twitter.com/DuncNisbet"&gt;@DuncNisbet&lt;/a&gt;), Alexandru Rotaru (&lt;a href="https://twitter.com/altomalex"&gt;@altomalex&lt;/a&gt;), Oana Casapu, Simon Schrijver (&lt;a href="https://twitter.com/SimonSaysNoMore"&gt;@SimonSaysNoMore&lt;/a&gt;), Zeger Van Hese (&lt;a href="https://twitter.com/TestSideStory"&gt;@TestSideStory&lt;/a&gt;), Helena Jeret-Mäe (&lt;a href="https://twitter.com/HelenaJ_M"&gt;@HelenaJ_M&lt;/a&gt;), Aleksis Tulonen (&lt;a href="https://twitter.com/al3ksis"&gt;@al3ksis&lt;/a&gt;), Anders Dinsen (&lt;a href="https://twitter.com/andersdinsen"&gt;@andersdinsen&lt;/a&gt;) - at the awesome &lt;a href="http://www.karlskronatestgathering.se/titan.html"&gt;TITAN peer conference&lt;/a&gt; in Karlskrona, Sweden.&lt;/p&gt;
&lt;p&gt;During the conference we discussed leadership and testing and on Sunday morning I got the opportunity to tell my story&lt;sup id="fnref:1"&gt;&lt;a class="footnote-ref" href="https://smallsheds.garden/blog/2015/two-styles-of-leadership-in-spreading-context-driven-testing-titanconf/#fn:1"&gt;1&lt;/a&gt;&lt;/sup&gt;. (I do wish I had captured more of the discussion afterwards to include in this blog post.)&lt;/p&gt;
&lt;h3&gt;The first style&lt;/h3&gt;
&lt;p&gt;When thinking about my own leadership in testing, one of the first things that come to mind are my attempts to influence my colleagues at work (testers, developers, project managers) to become more context-driven in their attitude towards testing.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://smallsheds.garden/blog/2015/two-styles-of-leadership-in-spreading-context-driven-testing-titanconf/"&gt;Read more…&lt;/a&gt; (5 min remaining to read)&lt;/p&gt;&lt;/div&gt;</description><category>context-driven testing</category><category>leadership</category><category>peer conferences</category><guid>https://smallsheds.garden/blog/2015/two-styles-of-leadership-in-spreading-context-driven-testing-titanconf/</guid><pubDate>Sun, 06 Sep 2015 17:56:54 GMT</pubDate></item><item><title>DEWT3 experience report</title><link>https://smallsheds.garden/blog/2013/dewt3-experience-report/</link><dc:creator>Joep Schuurkes</dc:creator><description>&lt;div&gt;&lt;p&gt;Last weekend the third Dutch Exploratory Workshop in Testing (DEWT3 for short) took place. The ingredients were: a very nice hotel in the woods, lots of talk about testing, beer, whiskey, a small to moderate amount of sleep, stickies and a group of fun and interesting people (You can see them &lt;a href="http://dewt.wordpress.com/2013/04/24/dewt3-experience-reports/"&gt;here&lt;/a&gt;.)&lt;/p&gt;
&lt;p&gt;On Saturday the talks (and thus discussions) were about systems thinking. A few years ago I did read Jerry Weinberg's "An Introduction to General Systems Thinking" and although a very interesting read, w.r.t. to applying it to testing I never got further then: Software is (part of) a system, so you can apply systems thinking to it. Of course, that's very much true, but it's also quite a vague piece of advice.&lt;/p&gt;
&lt;h3&gt;A primer on systems thinking&lt;/h3&gt;
&lt;p&gt;Enter James Bach, who kicked off DEWT3 with a primer on systems thinking. Systems thinking is just a way of thinking - just like logical thinking, analogical thinking, creative thinking, etc. - in which we approach a situation as being a system. So what's a system? It's a set of things in a meaningful interaction with each other.
This definition raises all sorts of questions relevant in systems thinking:&lt;/p&gt;
&lt;p&gt;&lt;a href="https://smallsheds.garden/blog/2013/dewt3-experience-report/"&gt;Read more…&lt;/a&gt; (5 min remaining to read)&lt;/p&gt;&lt;/div&gt;</description><category>context-driven testing</category><category>DEWT</category><category>peer conferences</category><category>systems thinking</category><guid>https://smallsheds.garden/blog/2013/dewt3-experience-report/</guid><pubDate>Sun, 28 Apr 2013 13:32:02 GMT</pubDate></item><item><title>Let's Test 2012 - time travel advice</title><link>https://smallsheds.garden/blog/2012/lets-test-2012-time-travel-advice/</link><dc:creator>Joep Schuurkes</dc:creator><description>&lt;div&gt;&lt;p&gt;If I had a time machine and could travel back in time to give myself some advice before attending &lt;a href="http://lets-test.com/"&gt;Let's Test 20212&lt;/a&gt;,
it would be this:&lt;/p&gt;
&lt;p&gt;- Go!&lt;br&gt;
- Don't worry too much about which session to attend. One of the most valuable sessions you will attend, you'll choose because it has the least appealing abstract.&lt;br&gt;
- Bring your running gear.&lt;br&gt;
- If you ask Rikard Edgren nicely, he will give you a dead-tree version of his '&lt;a href="http://www.thetesteye.com/papers/TheLittleBlackBookOnTestDesign.pdf"&gt;Little Black Book on Test Design&lt;/a&gt;'.&lt;br&gt;
- Enjoy the food. Don't worry, it's not much of a challenge.&lt;/p&gt;&lt;p&gt;&lt;a href="https://smallsheds.garden/blog/2012/lets-test-2012-time-travel-advice/"&gt;Read more…&lt;/a&gt; (1 min remaining to read)&lt;/p&gt;&lt;/div&gt;</description><category>conferences</category><category>context-driven testing</category><guid>https://smallsheds.garden/blog/2012/lets-test-2012-time-travel-advice/</guid><pubDate>Fri, 18 May 2012 17:32:08 GMT</pubDate></item></channel></rss>