<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Chris Miles on Medium]]></title>
        <description><![CDATA[Stories by Chris Miles on Medium]]></description>
        <link>https://medium.com/@ceemiles?source=rss-87088195047d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*IipSqbY3H4ckR_rSBMiuMg.jpeg</url>
            <title>Stories by Chris Miles on Medium</title>
            <link>https://medium.com/@ceemiles?source=rss-87088195047d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 13:39:44 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ceemiles/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Without testing there is no development]]></title>
            <link>https://medium.com/@ceemiles/without-testing-there-is-no-development-2872737ab342?source=rss-87088195047d------2</link>
            <guid isPermaLink="false">https://medium.com/p/2872737ab342</guid>
            <category><![CDATA[testing]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Chris Miles]]></dc:creator>
            <pubDate>Thu, 08 Jun 2017 18:46:28 GMT</pubDate>
            <atom:updated>2017-06-11T18:51:40.288Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/512/1*xxhJR-ym40Y2fLkoAxMbNA@2x.jpeg" /></figure><p>I’ve been at the <a href="http://2017.theleaddeveloper.com/">Lead Developer</a> conference in London today. It’s schedule has a blend of leadership and technical talks that have been both inspiring and thought provoking.</p><p>Testing has been given plenty of mentions. Usually like this, “… you know for testing, [<em>dramatic</em> <em>pause</em>] but nobody tests anyway!”, everyone laughs, or “you must automate all the tests” everyone nods and takes pictures of the slide.</p><p>700 lead developers going back to leading and inspiring their teams, sharing a casual joke about testing and recommending we automate all the things.</p><p>This I hope is not the message people take home.</p><h4>Preserve dignity</h4><p>Anjuan Simmons explained leadership lessons we can learn from the agile manifesto. He said,</p><blockquote>“preserve dignity at all cost”</blockquote><p>So please, stop taking a pop at testing, I know it’s easy to do, I’ve done it myself plenty of times (self effacing humour, a cultural thing I guess, we’ve covered that plenty today). Here’s the thing though, it’s not cool and it’s really not ok. People didn’t like it when jokes were made about Java and PHP but testing was fair game. At this point I should point out that this is a very inclusive conference and it’s clear there’s no room for haters here. If you are in a tech leadership role you should really check it out, it’s all on <a href="https://www.youtube.com/channel/UCmM3eCpmWKLJj2PDW_jdGkg">YouTube</a> (or will be shortly).</p><p>Here’s the confessional part, I’m a tester or at least, that’s how I got to where I am today.</p><h4>Thank you</h4><p>Erika Carlson talked passionately about fearless feedback for software teams. She advocated (apologies for paraphrasing here), “thank you” when you get feedback, even if the feedback is hard to hear.</p><p>So to all those who laughed, thank you. Following another of Erika&#39;s suggestions I sat and thought about this feedback.</p><h4>Skunk Works</h4><p>Then something unexpected happened. We finished with a brilliant talk from Nickolas Means on the original Skunk Works. If you don’t know the history get to Google, it’s fascinating (and the circus tent image will be explained).</p><p>Over the course of 45 minutes we learned how the Lockheed Skunk Works developed amazing planes in no time at all that could do things no plane ever should. Yay developers!</p><p>But wait let’s look a bit closer. The story starts with some tests. That new plane won’t work. Many iterations of build and test later it works. So they do some more and it’s more amazing, they prototype using a mock (jet engine) and then test it with the real engine when they get it. They build a plane full of defects they understand and find ways to (literally) prop it up. Finally they pull in a load of bits of stuff built for other purposes and cobble it into a plane that can’t actually fly but they test and understand it’s limitations and write software that keeps it in the air.</p><h4>What is development if you do not test?</h4><p>Google “develop” and it’ll give you this,</p><p>“Develop - To grow or cause to grow and become more mature,advanced, or elaborate.”</p><p>To develop means to mature and advance, to do this you have to iterate, to iterate you need to learn about the thing you built and to learn about the thing, you need to test (a long way of saying build, measure, learn). So if you don’t test you are not developing, you are just assembling.</p><p>Next time you joke about not testing reflect on what that means about your development.</p><h3>Some feedback for you</h3><p>Maybe you have had a bad experience with testers, it happens more than it should, but perhaps you could think about how you hired them (that’s some feedback by the way, you’re welcome ☺️).</p><p>There’s lots of places you can learn about the testing craft, <a href="https://www.ministryoftesting.com/">Ministry of Testing</a> is a good place to start, watch some of the talks from TestBash (or go, they are literally everywhere these days). Find out why you can’t possibly automate all the tests (or really any of them) and find out what you’ve missed if you think you have.</p><p>I’ll leave you with a quote from the excellent Micheal Bolton (no not that one, you really should try to learn more about testing),</p><blockquote>“Testers extend the senses of the development team. Testers, and testing, are part of the development process”</blockquote><p>It would be lovely to think that some of those 700 lead developers (well 698, I spotted at least one other tester in the crowd) might be returning to work on Monday explaining to their teams just how valuable tests are.</p><p>And thanks again for the feedback.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2872737ab342" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Of Quookers and Kettles or The Inefficiency of Efficiency.]]></title>
            <link>https://medium.com/@ceemiles/of-quookers-and-kettles-or-the-inefficiency-of-efficiency-ed0f374cc72d?source=rss-87088195047d------2</link>
            <guid isPermaLink="false">https://medium.com/p/ed0f374cc72d</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[collaboration]]></category>
            <category><![CDATA[corporate-culture]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Chris Miles]]></dc:creator>
            <pubDate>Wed, 05 Apr 2017 10:12:25 GMT</pubDate>
            <atom:updated>2017-04-05T18:04:23.986Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/512/1*jtse_EXGI5HKETn-phFGgQ@2x.jpeg" /></figure><p>An office I worked in installed a lovely boiling water tap, a <a href="http://www.quooker.co.uk/enuk">Quooker</a>. It was amazing, boiling water as soon as the tap was turned on. Tea was prepared in no time at all and people were free to get on with whatever they were doing. It was a major efficiency boost and pretty cool to boot.</p><p>Now I’ll tell you a tale of a maturing startup suffering growing pains. A clued up agile tech team suddenly at the mercy of a tyrannical HR department who failed to see the value in all the milling about and chatting (cause that’s basically agile right?). The tea room became a sanctuary where it was still acceptable to talk to friends and colleagues, foster relationships and discuss the vexing problems of the day.</p><p>Making a cup of tea, boiling the kettle, letting it brew, ten minutes away from your desk. Rarely are you on your own, the kitchen is a popular place, the kettle boils more water than you need, but not necessarily enough for everyone who wants it. You’re going to need to talk to one another, collaborate and maybe engage in a random act of kindness.</p><p>There we have it, the magic of the kitchen, the great leveller, the one place that everyone visits.</p><p>So, which is more efficient, a quick chat in the tea room when you’ve all stepped away from your desk or a half hour planned meeting that interrupts you mid-flow? Those efficiencies aren’t stacking up quite so well.</p><p>When you are trying to foster team collaboration remember it’s often the mundane tasks that bond us, not the grand gestures. These tasks can become rituals that bond teams further. Are your efficiencies hostile to collaboration?</p><blockquote>Are you losing the opportunity for an interaction?</blockquote><p>So next time you are looking for efficiency be mindful of the cost. Are you losing the opportunity for an interaction? Are you introducing unexpected inefficiencies?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ed0f374cc72d" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>