<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>blog on jelrikvh</title>
    <link>https://jelrikvh.nl/posts/</link>
    <description>Recent content in blog on jelrikvh</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-gb</language>
    <lastBuildDate>Mon, 11 Jan 2021 16:32:13 +0200</lastBuildDate><atom:link href="https://jelrikvh.nl/posts/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>code reviews are bad</title>
      <link>https://jelrikvh.nl/posts/code-reviews-are-bad/</link>
      <pubDate>Mon, 11 Jan 2021 16:32:13 +0200</pubDate>
      
      <guid>https://jelrikvh.nl/posts/code-reviews-are-bad/</guid>
      
      <description>&lt;p&gt;Deliver better software, faster.&lt;/p&gt;
&lt;p&gt;Yes. This is a clickbait-y title. Let me expand on it a little bit: how most development teams I know do code reviews is detrimental to delivering quality software.&lt;/p&gt;
&lt;p&gt;&lt;img src=&#34;checkboxes.jpg&#34; alt=&#34;three emoji with checkboxes next to them&#34;&gt;&lt;/p&gt;
&lt;p&gt;A lot of questions need answering here. What’s a code review? What is quality in software? What’s “delivering”? And if code reviews are so bad, should there be an alternative? If so, what is it? Let’s explore.&lt;/p&gt;</description>
      
    </item>
    
    <item>
      <title>liberating what?</title>
      <link>https://jelrikvh.nl/posts/liberating-what/</link>
      <pubDate>Wed, 06 Mar 2019 16:32:13 +0200</pubDate>
      
      <guid>https://jelrikvh.nl/posts/liberating-what/</guid>
      
      <description>&lt;p&gt;&lt;em&gt;Untangling our broken ways of working with Liberating Structures&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;When we’re solving problems, we work together. We have meetings, we create planning documents and distribute them, we move post-it notes from one side of a wall to another, we talk during our breaks or at the coffee machine.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;What if I told you that the way we work together is fundamentally broken?&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;Have you ever walked into a workgroup meeting and felt the energy draining from your body the very instant you entered the room? Did you ever experience a strategic presentation in which almost every attendant was busy on their phones? Is their laptop the most important thing people seem to bring to a conversation? Have you ever wondered why some people just never seem to speak up? Or why it’s always the same people that do all the talking?&lt;/p&gt;</description>
      
    </item>
    
    <item>
      <title>liberating structures in practice: the ux fishbowl</title>
      <link>https://jelrikvh.nl/posts/liberating-structure-in-practice-the-ux-fishbowl/</link>
      <pubDate>Wed, 06 Mar 2019 12:12:33 +0200</pubDate>
      
      <guid>https://jelrikvh.nl/posts/liberating-structure-in-practice-the-ux-fishbowl/</guid>
      
      <description>&lt;p&gt;&lt;em&gt;Shift your perspective and see an experience through someone else’s eyes.&lt;/em&gt;&lt;/p&gt;
&lt;h2 id=&#34;the-setting&#34;&gt;The setting&lt;/h2&gt;
&lt;p&gt;A few months back, &lt;a href=&#34;https://medium.com/@maxbrouwer&#34;&gt;Max Brouwer&lt;/a&gt; and I hosted a workshop for the management team of Wonderkind. The product team of Wonderkind, including the CTO, Head of Development, and Product Owner recognised that the team needed to make tough priority choices. We facilitated the conversations that needed to happen and helped them create a first version of their roadmap. The whole day had been a string of liberating structures, like Impromptu Networking, Appreciative Interviews, and Purpose-To-Practice.&lt;/p&gt;</description>
      
    </item>
    
  </channel>
</rss>
