<?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 David Campey on Medium]]></title>
        <description><![CDATA[Stories by David Campey on Medium]]></description>
        <link>https://medium.com/@davidcampey?source=rss-210438420dbd------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*z_7m5D3KyZVkCwC9.jpeg</url>
            <title>Stories by David Campey on Medium</title>
            <link>https://medium.com/@davidcampey?source=rss-210438420dbd------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 00:24:28 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@davidcampey/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[Backlog blockage]]></title>
            <link>https://medium.com/@davidcampey/backlog-blockage-8d98f658f0fc?source=rss-210438420dbd------2</link>
            <guid isPermaLink="false">https://medium.com/p/8d98f658f0fc</guid>
            <category><![CDATA[flow]]></category>
            <category><![CDATA[iteration]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[lean]]></category>
            <dc:creator><![CDATA[David Campey]]></dc:creator>
            <pubDate>Mon, 07 Aug 2023 10:20:38 GMT</pubDate>
            <atom:updated>2023-08-07T10:38:36.210Z</atom:updated>
            <content:encoded><![CDATA[<p>Building a backlog of stories and burning through that based on priority is a starting point on most Agile journeys.</p><p>The backlog really seems to be a good idea, makes for a great start, but usually gets frustrating. Frustratingly long, frustratingly hard to manage, and frustratingly confusing.</p><p>In this post I’ll unpack why this is frustrating, how attempts to fix it can make it worse, and share some patterns that are useful in resolving it, in particular Iteration Design.</p><h4>Queue Frustration</h4><p>This frustration stems from the fact that a backlog is really is a queue. A queue that may get re-ordered by prioritization.</p><p>Queues ultimately <strong>block the flow of value</strong>.</p><blockquote>“A queue is the duration of time something is ready to be worked on, but is waiting for someone to work on it”<br> — <a href="https://www.playbookhq.co/blog/lean-project-management-principles">Lean Project Management Principles</a>, by <a href="https://www.playbookhq.co/blog/author/elyssa-pallai">Elyssa Pallai</a></blockquote><p>In this case, the flow of value is the process in the delivery of valuable software and can be observed by looking at the cycle time, that is, the timeline from when we decide to do something to when it is done.</p><h4>Ideal Backlog Flow</h4><p>As an example of the perfect world, we think about our product and need to do four things.</p><ul><li>Item #1 is the most valuable, so we put it first</li><li>once we have “Done” it, it ships, and</li><li>we move onto #2,#3,#4 &amp;c.</li></ul><figure><img alt="Sketch of a kanban board with four items in the left column, a dotted path to the right of the top item shows how it will progress through the columns." src="https://cdn-images-1.medium.com/max/892/1*r0st6gKZrkgjkXrR423YZg.jpeg" /><figcaption>Idealised kanban flow in theory</figcaption></figure><p>In this scenario, those stakeholders who care about #4 know they’re in the queue, and will need to wait for #1, #2 and #3 to be worked on &amp; ship before we get to them. This is acceptable, and reasonable.</p><h3>How things go…</h3><p>Let’s assume things start well and we finish #1 as planned, then go onto start #2 immediately.</p><p>BUT, as we’re continuing on #2, there is feedback from user testing on #1 and changes are suggested, so we need to decide whether to</p><ul><li>continue with #2 and stick to the plan,</li></ul><p>or</p><ul><li>go back and improve #1 (which we previously decided was the highest priority).</li></ul><p>This can lead to a pretty violent game of “who’s right” debating whether the plan is right, or we delivered the right thing, or the feedback is right, or we needed a bigger definition of done, or we should have had a better definition of ready.</p><h3>Review loop-hole</h3><p>The mature team will use reviews as an opportunity to introduce new stories and prioritize them based on feedback. So we add #1A and #1B at the top of the queue, and perhaps #1C lower down.</p><figure><img alt="Sketch of a kanban board with items in the left column, item #1 is in the done column, but has loops back to the backlog column to insert #1A, #1B and #1C" src="https://cdn-images-1.medium.com/max/982/1*yzY9tZUK8LYQfqqeWCUzSg.jpeg" /><figcaption>Turbulent kanban flow in reality</figcaption></figure><p>This is great <em>and right</em> as it lets us make important improvements to the most important story. It also relegates other suggestions to lower in the backlog.</p><p>The downside is the lower prioritized stories (which we’d promised to work on next), end up having a much longer cycle time, and quickly that inventory rots and needs constant grooming.</p><p>This results in a tricky situation if we’re contracted (explicitly or implicitly) to march sequentially through the back-log, the team is doomed to lose that game of who’s right.</p><h3>Two flight levels</h3><p>This is particularly an issue as some people in the organisation have a much higher-level view of things than those doing the work, leading to mismatched expectations as in this example:</p><blockquote>“Um, it’s been 3 months since you said you’d do this feature <strong>next,</strong> and you haven’t started yet.” <br> — the sales team.</blockquote><p>vs</p><blockquote>“Hey, wait! We’re getting things done quickly and working really hard!” <br> — the dev team.</blockquote><p>The issue is that there are two value streams, one embedded in the other.</p><ol><li>The outer is the user-facing plan used to talk to customers, and</li><li>The inner is the dev-facing plan used to define and refine the functionality.</li></ol><p>Klaus &amp; Cliff’s work on <a href="https://www.flightlevels.io/flightlevels/">Flight Levels</a> explores ways we can make work visible at strategic, co-ordination and operational levels, that can help business agility by separating these different layers of work in multiple kanban flight levels.</p><p>From the flight level of sales, the cycle time of their user-facing commitments makes sense. From the flight-level of the developer, the dev-facing stories are king.</p><p>Making it visible doesn’t solve the tension but it can make it possible to explore ways to improve together.</p><h3>WIP it into shape?</h3><p>We could make a kanban-style Work-In-Progress (WIP) limit on the “to-do” or “in progress” column of the outer value stream. This solves for the immediate problem, as not allowing too many lower priority stories to be backlogged ultimately results in a better cycle time.</p><p>This would also be incredibly frustrating. It would not provide any sense of context and understanding where we’re going, as well as perhaps introducing too much slack waiting for feedback.</p><blockquote>“Oh, we still need to know where we’re going? Why not add those stories to the backlog?” <br>“We’re limiting WIP? Okay, maybe not that backlog, but let’s make a list over here because we don’t want to forget about these things.”</blockquote><p>And we’ll prioritize and sequence our outer list. Great. Now we have an outer-outer value stream queue. Cycle time inner loop hell.</p><p>Refrains of “We never get anything done” vs “We’re always getting things done”.</p><p>And both sides are, sadly, right.</p><h3>Okay, what do we do then?</h3><p>This tension exists because different parts of the organization are pulling and pushing product development from different perspectives, optimizing for their different needs.</p><p>If alignment around shared goals is the ultimate objective, we need a way to agree on what those goals &amp; priorities are.</p><blockquote>“Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.”<br> — Principles, Manifesto for Agile Software Development <a href="https://agilemanifesto.org/principles.html">agilemanifesto.org</a></blockquote><p>This “highest priority” is great as a principle but doesn’t address <em>how</em> to ensure we continue the delivery of (the most) valuable software. The CEO and the business have a set of priorities and plans that need to interface with the complex domain of iterative software development.</p><p>This is a problem many successful product teams are intuitively solving, but having to force it against the underlying way the work is organised in a backlog generates dissonance and friction, so it would really help if we could change how we frame the work to make it flow more smoothly.</p><h3>Iteration Design</h3><p>Working with this tension led to an approach I call “Iteration Design”.</p><p>We design step-by-step, only putting into writing in the plan what we next need to do to improve the product in the desired dimension.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*Uei0OsHmPFulrZzi75qIlw.png" /><figcaption>Conceptual flow of Iteration Design, from Customer Jobs through to “One Day” solution</figcaption></figure><p>In each iteration of iteration design, we:</p><ol><li>Use the value proposition canvas as a base to understand the how the product fits the customer jobs, pains and gains.</li><li>Identify where the biggest opportunity for pain reduction or gain creation is.</li><li>Conceive a change to the product that could improve those, focusing on specific improvements.</li><li>Build and deploy that change to customers.</li></ol><p>Then we go back to step 1 to review the product in light of the improvement and decide what to plan for the next iteration.</p><h3>What about Vision?</h3><p>As we lead ourselves and others through a difficult product development process, it is critical to have a vision of where we’re going.</p><p>In iteration design we encourage that dreaming and put that future at the end of the board after an undefined number of iterations towards it, with an explanation of how each Customer Job would ideally get done in the “one day” scenario, being as fanciful as we like.</p><p>We need to also accept that by the time we get there it will probably look very different to how we imagine it right now. This generally gets a resounding confirmation from CEOs and senior leadership who hold the vision.</p><p>The frustration comes from trying to slice up and map out a defined course to that vision, when no one really knows how we’re going to get there.</p><h3>Finding our way</h3><p>An uncertain environment like new product development, is like climbing an unmapped mountain.</p><p>Designing a detailed turn-by-turn series of instructions is clearly not going to work to get to the top of the mountain. We need to explore, learn and take it step-by-step.</p><p>Likewise, organisations and teams need to be able to point to the vision, to their summit, and then find the way there step-by-step, handling what they learn along the way.</p><p>This allows for a system that feels responsive, because it is responsive. We have cut out the waste of months of backlog to wade through. Rather we’re engaged spending our time connecting to what’s alive in the customer and the product and figuring out each next step together.</p><p>Iteration design is a pattern that helps to allow this wayfinding to happen more naturally, and to design our systems of work to be coherent with the underlying nature of the work.</p><h3>Further Reading</h3><p>For more on this see:</p><ul><li>this <a href="https://www.youtube.com/watch?v=PtQInS4fVr8&amp;list=PLX2zxVsSz_Xpla6Jnlc8gHEu3b0M6-XBG&amp;index=7&amp;ab_channel=LeanIterator">iteration design video</a> in our Lean Iterator Course on YouTube</li><li>Jeff Patton’s “<a href="https://www.jpattonassociates.com/story-mapping/">Story Mapping</a>” provides a useful way to lay out the work, that we typically move to using in practice once a team gets into flow.</li><li>John Cutler lays out a lovely system of work embracing a series of “bets” and how they flow towards becoming reality in his post on “<a href="https://www.linkedin.com/pulse/basics-john-cutler/">The Basics</a>”.</li></ul><blockquote>“Don’t burn your features, iterate customer journeys”</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8d98f658f0fc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Motivation Vector Math]]></title>
            <link>https://medium.com/@davidcampey/motivation-vector-math-3d1cd8e00c8f?source=rss-210438420dbd------2</link>
            <guid isPermaLink="false">https://medium.com/p/3d1cd8e00c8f</guid>
            <category><![CDATA[motivation]]></category>
            <category><![CDATA[mind]]></category>
            <category><![CDATA[psychology]]></category>
            <category><![CDATA[math]]></category>
            <category><![CDATA[development]]></category>
            <dc:creator><![CDATA[David Campey]]></dc:creator>
            <pubDate>Thu, 25 Aug 2022 13:10:59 GMT</pubDate>
            <atom:updated>2022-08-25T20:37:29.403Z</atom:updated>
            <content:encoded><![CDATA[<p>Here’s a mathematical model I find useful in thinking about motivation. Call it a mind hack if you will.</p><h3>Vector Math</h3><p>If you did some vector math, this diagram will be familiar to you:</p><figure><img alt="Vector diagram with two vectors showing the geometric interpretation of the dot product, and how the projection of the one onto the other is the magnitude of the dot product." src="https://cdn-images-1.medium.com/max/538/1*vg2o_PZNUMjYVE6ETA32sg.png" /><figcaption>Geometrical Meaning of Dot Product from <a href="https://www.cuemath.com/algebra/dot-product/">cuemath</a></figcaption></figure><p>If you didn’t do the math or need a refresher, what it says is if you take the dot product a.b , you end up with the projection of aonto b, or how much of the effort of a moves you in the direction of b . This is proportional to the magnitude (length)of a and b too.</p><p>If they are lined up, this is maximised, if they are orthogonal (90 degrees) it is zero, and if it is opposed, it is negative.</p><p>So what does this have to do with motivation?</p><p>action . intention = motivation</p><p>We generate motivation by doing what we intended to do.</p><p>So if you do something you want to do, the vectors are aligned and you generate motivation.</p><p>😃😄😂If you really want to do it, motivation generated by doing it is more.</p><p>😅/😓The more effort you put into it, the more it could have an effect.</p><p>🤷🏻‍♂️..😒 If you do something you “sort of” want to do, you can see low motivation results.</p><p>😒😠👿Doing something you are opposed to doing, that you think is wrong or just don’t want to do, generates negative motivation.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FMbLgtT1Ba4s%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DMbLgtT1Ba4s&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FMbLgtT1Ba4s%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/838c71ad2c43ffc7be154416a11d7ed3/href">https://medium.com/media/838c71ad2c43ffc7be154416a11d7ed3/href</a></iframe><h4>Some examples</h4><ul><li>When you’re waiting in line at the bank.</li><li>When finishing that “little task” takes longer than expected.</li><li>When you get something you’ve been looking forward to (and it’s great)</li><li>When you score the winning points in a game.</li><li>Working on your tax return… .. .</li></ul><h3>Why this works</h3><p>When our brain perceives that reality has moved in line with our expectations we reinforce that behaviour and those expectations. At a basic level this generates dopamine, or as I like to call it “hope-amine”.</p><p>In reality there isn’t just one thing that we want, so we take the dot product of our actions against a large number of different hopes, and add up the resulting motivation.</p><p>Then there’s a reinforcing loop of that extra motivation intensifying intent and giving more energy for action, but that’s another delightful story… (what I call the <a href="https://www.youtube.com/watch?v=sH4NvrxalWg">loop of joy</a>)</p><h3>So what?</h3><p>Well, Dave, that’s a nice model. How can I use it?</p><h4>Inspect &amp; Adapt in a Dev Team</h4><p>When deep in software development, it is useful to pop your head up and review your expectations.<br>e.g. these approaches in a product development team:</p><ul><li>Hourly @ personal scale: pomodoro, task lisk, personal kanban;</li><li>daily @ team scale: stand-up, task board;</li><li>week-scale: review &amp; retro.</li></ul><blockquote>Are we on track?<br>Do we need to change our expectations?<br>Or change our actions?</blockquote><figure><img alt="Time-lapse photo of a starry night sky full of cool-coloured stars, generating a swirling vortex of star-light, it’s centre point slightly above a person silhouetted in the foreground." src="https://cdn-images-1.medium.com/max/1024/0*ppkHahyOtTQavu2e" /><figcaption>The firmament swirling around a perspective, Photo by <a href="https://unsplash.com/@jeremythomasphoto?utm_source=medium&amp;utm_medium=referral">Jeremy Thomas</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h4>Value shift to move Intentions</h4><p>“What you’re doing right now is an expression of your highest values. Not the values you want to have, but the values you actually have.” Dr Di Martini</p><p>At an individual level, our rational brains may say that we value different things to what we actually value at a deeper level.</p><p>e.g. if I say “I want to get fit &amp; healthy” but: I’m lying in bed snoozing instead of getting to gym. <br>The value I actually have is “comfort”. The values I want to have are “health &amp; activity”.</p><p>This creates a confusing mix of intention vectors where different parts of your brain are wanting different things.</p><p>How do we align our minds and shift the values we actually hold?</p><p>One tool in this space is to use a practice of <a href="https://www.berkeleywellbeing.com/daily-affirmations.html">daily affirmations</a> to shift that needle.</p><h4>Don’t be insane</h4><p>Einstein’s classic definition of insanity is “doing the same thing over and over again and expecting different results.”</p><p>If your actions are not lining up with your intentions, you can of course “just” change your actions. But in reality that is a big “just” as usually our actions result from a system of behaviour that needs conscious effort to change.</p><h4>Balance in the force</h4><p>Changing both our intentions and our actions to be in alignment takes effort in itself.</p><p>Building a desire for that can be the first step on a path that leads to a fulfilling and rewarding life, generating energy and motivation and avoiding frustration or suffering.</p><figure><img alt="Stack of greyish rocks, one big rock has moss on it, larger rocks in a central stack, and some smaller ones on top, a few little ones stacked off to one side, a long tiny one in the stack of smaller ones on top. With blurred background of a riverbed and some bushes." src="https://cdn-images-1.medium.com/max/1024/0*FQuu7wMSf-nN0UE5" /><figcaption>Photo of little rocks finding balance by <a href="https://unsplash.com/@arstyy?utm_source=medium&amp;utm_medium=referral">Austin Neill</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>This model is definitely not perfect, but it has helped me, and helped me to help others in coaching conversations over the years.</p><p>I hope that understanding this model might help you in navigating the meh, and finding the woot.</p><p>\o/</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3d1cd8e00c8f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Team Needs…]]></title>
            <link>https://medium.com/@davidcampey/the-team-needs-dceb823c7bfc?source=rss-210438420dbd------2</link>
            <guid isPermaLink="false">https://medium.com/p/dceb823c7bfc</guid>
            <category><![CDATA[continuous-integration]]></category>
            <category><![CDATA[coaching]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[non-violent-communication]]></category>
            <category><![CDATA[teamwork]]></category>
            <dc:creator><![CDATA[David Campey]]></dc:creator>
            <pubDate>Thu, 28 Jul 2022 16:18:43 GMT</pubDate>
            <atom:updated>2022-07-28T17:13:44.576Z</atom:updated>
            <content:encoded><![CDATA[<p>Imagine you could get your tech team what it needs to succeed.<br>Do you know what that is? <br>How do we find out? <br>How do we meet those needs?</p><figure><img alt="Photo of a tangled string of Christmas lights in the dark, with the small pools of of multicoloured light illuminating the wires that connect them." src="https://cdn-images-1.medium.com/max/1024/0*atxOVDpJQCOFYbq9" /><figcaption>Photo of a tangled string of Christmas lights in the dark, with the small pools of multicoloured light illuminating the wires that connect them by <a href="https://unsplash.com/@ridhamparikh?utm_source=medium&amp;utm_medium=referral">Ridham Parikh</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h4><strong>What do tech teams need? What do any of us need?</strong></h4><p>This is an important question and one that I have been pondering for at least the past 7 years, since hearing someone at a Scrum Gathering using pointed language about addressing what people need.</p><p>I later learned that this wise soul (who prefers not to be named) was talking <a href="https://www.cnvc.org/learn-nvc/what-is-nvc">Marshall Rosenberg’s language of non-violent communication</a>, where connecting to what we need, can in turn connect us to what is alive in us and allow us to play the game of “make life wonderful for everyone”.</p><p>In this quest, I was initially at a loss for words, concepts or even a framework (unusual for me!). Luckily the Centre for Non-Violent Communication has a handy <a href="https://www.cnvc.org/training/resource/needs-inventory">inventory of needs</a>, and <a href="https://www.cnvc.org/training/resource/feelings-inventory">inventory of feelings</a>, which are useful to start exploring as a catalog. We have since explored in reflections and retrospectives trying to connect to our individual human needs.</p><h4><strong>What are needs vs wants/demands/plans?</strong></h4><p>Often, when we talk about what we need, we frame it in a demand or a plan, like:</p><blockquote>“we need a CI server”<br>“we need unit tests”<br>“we need management to get off our backs”<br>“we need to deliver by the 15th of Octember!”</blockquote><p>That language communicates how we want to get our needs met, but not our actual needs, and disconnects us from what is alive in us.</p><p>To me as a programmer, it is like having implementation code without tests. I struggle to ensure the implementation does the right thing without knowing the intent. And it becomes really difficult to suggest or make changes to the implementation if we’re not sure of the why.</p><h4><strong>A new syntax for requests</strong></h4><p>Non-violent communication suggests practicing with language in the following structure to bend our minds back into connecting to our needs.</p><p>When: thing that objectively happened<br>I felt: feeling that I personally felt<br>Since my need for: need<br>Was met / not met.<br>I request: something specific and do-able.</p><p>Trying to get back and start with playing this forwards can be incredibly frustrating in practice, but we can play it backwards to try to re-connect to the need in ourselves or others.</p><h4><strong>An adventure from request to need</strong></h4><p>When we hear Amy &amp; Bob’s request for a CI server, we can ask them: “What need would this meet?” and have a look in the <a href="https://www.cnvc.org/training/resource/needs-inventory">needs inventory</a>…</p><blockquote>“Hrm, okay… getting a CI server would meet my need for…<br>“clarity,”<br>“stability, order” <br>“the need to be heard,” <br>“Yeah!”</blockquote><h4><strong>Upping the aliveness with feelings when needs are met</strong></h4><p>Then we can ask Amy &amp; Bob: “How would you feel if these needs were met?” and have a look in the <a href="https://www.cnvc.org/training/resource/feelings-inventory">feelings inventory</a>…</p><blockquote>“When my need for clarity is met, I feel… relaxed and calm”</blockquote><blockquote>“When my need for stability is met, I feel… empowered, safe and secure”</blockquote><blockquote>“When my need for order is met, I feel… clear-headed and relaxed”</blockquote><blockquote>“When my need to be heard is met, I feel… inclusion, respect and belonging”</blockquote><p>Oooh, that’s starting to hum.</p><h4><strong>Connecting to feelings when needs are NOT met</strong></h4><p>Then we can ask ourselves: “How would you feel if these needs were NOT met?” and have a look in the feelings inventory…</p><blockquote>“When my need for clarity is NOT met, I feel… hesitant, lost, removed”</blockquote><blockquote>“When my need for stability is NOT met, I feel… insecure, reserved, apprehensive”</blockquote><blockquote>“When my need for order is NOT met, I feel… edgy, stressed out, overwhelmed”</blockquote><blockquote>“When my need to be heard is NOT met, I feel… resentful, alienated, uninterested”</blockquote><p>Ooof. That hurts to even write down hypothetically.</p><h4><strong>Connecting to reality with examples</strong></h4><blockquote>“For example, when…”</blockquote><blockquote>“When I was wanting to deploy to production last week, but I’m still waiting.”</blockquote><blockquote>“When I needed to rush a bugfix to prod and rolled back Bob’s changes inadvertently.”</blockquote><blockquote>“When I had to wake up at 7am so that we could deploy safely”</blockquote><blockquote>“When I see my ticket from 2 years ago to try out automating the 17 steps I have to run through every deploy.”</blockquote><h4>Connected to what’s alive</h4><p>If you’ve just taken this fictitious journey of words with me, you may feel a lot more connected to what’s alive in the fictitious request for a CI server. Perhaps you could imagine how connected to what’s alive in us we would feel when exploring how we might meet those needs.</p><p>Try to imagine the difference, once all of that has been allowed to flow into the pool of shared meaning, how that would change the nature of the conversation. How it might feel fulfilling the request, or brainstorming specific and do-able alternatives, compared to doing it without being connected to what’s alive.</p><h4>Do you imagine a more wonderful world?</h4><p>This is a world we are attempting to create every day when we attempt to stay connected to what’s alive in us in our communication.</p><p>I try to do that in my work at afrolabs and across the x-labs system of coaching and community by starting our continuous improvement with a reflection of the needs of the team, through the lens of the Team Needs Hexagon, and then we can start to ideate together and share.</p><p>Let’s meet our needs and together create the world we are longing for.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dceb823c7bfc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Emotions are first-class citizens]]></title>
            <link>https://medium.com/@davidcampey/emotions-are-first-class-citizens-acae8896d218?source=rss-210438420dbd------2</link>
            <guid isPermaLink="false">https://medium.com/p/acae8896d218</guid>
            <category><![CDATA[non-violent-communication]]></category>
            <category><![CDATA[conflict]]></category>
            <category><![CDATA[conversations]]></category>
            <category><![CDATA[citizen-engagement]]></category>
            <category><![CDATA[emotional-intelligence]]></category>
            <dc:creator><![CDATA[David Campey]]></dc:creator>
            <pubDate>Thu, 12 May 2022 08:36:25 GMT</pubDate>
            <atom:updated>2022-05-12T08:36:25.092Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*C8j7jtKR2yc4mck4" /><figcaption>Photo by <a href="https://unsplash.com/@aaronburden?utm_source=medium&amp;utm_medium=referral">Aaron Burden</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>For me, in my work, I say “emotions are first-class citizens”.</p><p>Why? What do I mean by this?</p><p>If we view our minds, and our conversations as communities, as societies, then our emotions are messengers to us.</p><p>They arrive, from the much bigger part of our mind, the subconscious, and have to contend with the other contents of consciousness. We can welcome those messengers as they arrive and allow their information into our minds and conversations, or we can treat them as unwelcome guests.</p><p>If we ignore them, however, we lose out on a lot of our intelligence and awareness.</p><p>If we can welcome them and include them, we can increase our access to our (collective) sub-conscious and intelligence.</p><p>But…</p><h3>Violence!</h3><p>Engaging with (or even sharing) emotions can be threatening and (violently) manipulative.</p><p>If they are not integrated into our mind’s and conversations society and become bad citizens, they can lead to triggering undesired side effects and violence.</p><p>(The same can be said about the ideas and impulses aka strategies that result in action, requests or demands we make.)</p><p>We need to figure out how these citizens can behave well. To welcome them, so they can be “well-come” if you’ll allow the play on words.</p><p>That is, when our consciousness contains emotions that arise, then we might engage with them in a non-violent way.</p><h3>A way of non-violence</h3><p>Marshall Rosenberg’s way proposed in NVC is to treat emotions (as well as ideas, impulses aka strategies) as messengers, expressions of an unmet need.</p><p>Then using our “giraffe ears” listen to them to point towards what they tell us about our needs, which can provide an opportunity to connect the conversation to what is alive in us.</p><figure><img alt="A happy person connecting to others over a video call while lying in her bed." src="https://cdn-images-1.medium.com/max/1024/0*61_-MCtxEfSItabu" /><figcaption>Photo by <a href="https://unsplash.com/@windows?utm_source=medium&amp;utm_medium=referral">Windows</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Once we have done that, have listened and established the connection back to our human needs, then the emotions and requests can flow in a non-violent way.</p><p>When this happens, we can together delight in meeting the needs, of ourselves and others, and re-learn to play the game how we might make life wonderful for everyone.</p><p>We can welcome these messengers into our minds and conversations with open arms, listen to their messages and understand them, and not be threatened by them.</p><p>They become “first class citizens”.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=acae8896d218" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Managing Agile DevOps with CAKE]]></title>
            <link>https://medium.com/@davidcampey/managing-agile-devops-with-cake-44273171bf54?source=rss-210438420dbd------2</link>
            <guid isPermaLink="false">https://medium.com/p/44273171bf54</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[cake]]></category>
            <category><![CDATA[software]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[David Campey]]></dc:creator>
            <pubDate>Mon, 18 Oct 2021 10:52:45 GMT</pubDate>
            <atom:updated>2021-10-18T11:32:30.960Z</atom:updated>
            <content:encoded><![CDATA[<p>One of my favourite management tools in software is cake. Yes, real, actual, literal cake.</p><p>It is deceptively simple, but simply planning for and buying cake, with two key questions:</p><ol><li>would this be a cake-worthy goal?</li><li>are we ready to eat the cake yet?</li></ol><p>(thankfully the cake is not an acronym, just put it in caps for emphasis on the CAKE, and/or to click-bait you— if you’re here, it worked)<br>(also the “Agile” and “DevOps”, they’re not really mentioned again in the article although it’s the subject area)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/560/1*YLfAM-5FmFKxn7-kaamZyQ.png" /><figcaption>🎂 cake 🎂</figcaption></figure><p>I have been doing it for a few years now, and have learned a few things I’d like to share about making work visceral.</p><p>To start with though, let’s go back to cake #1.</p><h4>An origin story</h4><p>I had the privilege to help a dev-ops team, called the “reliable deployments” team. It was a great team, tackling really hard problems moving from “word-doc based deploys” to fully automated, reliable deploys in a complicated enterprise stack.</p><p>The team had bonded around the lego movie and the “everything is awesome” song. We had a metaphor of being the roving knights slaying dragons and making the land safe for the people to live in, complete with the Muse “Knights of Cydonia” soundtrack in planning/review sessions.</p><p>But there was a problem — every time they got something demonstrable, the product owner would be happy and move them onto the next problem, before it was quite done. This meant that configuration, automation, documentation and all the other things that would make a dev-ops team proud and reduce work were getting skipped in favour of getting to the next big fire.</p><h4>Cake Order Form</h4><p>I had been enjoying Jonathan Rasmusson’s Inception Deck (from the Agile Samurai), as well as having a wry sense of amusement at the way forms work in bureaucracy. So I grabbed two A3’s and sketched up a Cake Order Form based on the Inception Deck.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7uOTRlKdccqZxAEUTnE1Ng.jpeg" /><figcaption>Original Cake Order Form, March 2015</figcaption></figure><p>It included things like: <br>— what is the goal, described in a short sentence <br>— draw the solution, a picture, typically a system diagram <br>— done when list, Enumeration of key achievables <br>— who is the team, Members and roles <br>and iirc the team all signed the form to “order the cake”.</p><h4>The two questions</h4><p>At design time we could ask the first question:</p><p><strong>1. “is it a cake-worthy goal?”</strong></p><p>and the team all contributed to what would or wouldn’t be cake-worthy. It was relatively intuitive to decide if it would be cake-worthy or not, and right-size it to ensure the goal was achievable in an imaginable time, as we wanted to eat cake</p><p>Then as the work happened, the work got to functional and the temptation to move on was there, and we could ask the second question:</p><p><strong>2. are we ready to eat cake yet?</strong></p><p>Now, no-one wants to eat a cake that they don’t feel is justified; it would lose its sweetness. This encouraged all to voice honest opinions on when we could order that cake!</p><h4>The cake arrives</h4><p>There is something magical about the arrival of the celebratory cake. It turns something imaginary and intangible — a software delivery into something tangible, edible, social. It makes the work visceral. It also is often met with disbelief — is this actually happening?!?</p><p>The email gets to go out “Cake in 5th floor kitchen — Reliable Deployments team celebrating getting [thing X] deploying automatically” Curious people come for cake, everyone hears about it, the chatter buzzes. The team are celebrated by their peers and colleagues.</p><h4>Eat the cake</h4><p>Taste sweet success, have the sugar and butter spike your happy chemicals, reminisce on the pain and the joy, reflect with peers, contemplate next steps in a relaxed way.</p><h4>Remember the cake</h4><p>Afterwards, the cake is memorable, it is visible, it is visceral, and visitors came. When we look back on the last few months, we remember those moments of cake and it feeds joy into our system, it builds faith. Joy and faith that are often lacking in the unix-style “silent success, loud failure” typical of engineering.</p><h4>Hope for cake</h4><p>The successful first cake is followed by the hope and expectation — what will our next cake be for? It becomes fun, engaging, exciting.</p><h4>How it went?</h4><p>Well, the first few cakes were ordered, the forms started working without my help, I was delighted.</p><p>When I checked back in on the team a few months later I was crest-fallen to hear them say they’d stopped ordering cake… until I found out they were teasing me a bit, and that they had stopped ordering cake and started ordering other comestibles instead, like burgers, or gatsbys. That was fantastic.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=44273171bf54" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Rudder Creates Resistance]]></title>
            <link>https://medium.com/@davidcampey/the-rudder-creates-resistance-cbd72c40c192?source=rss-210438420dbd------2</link>
            <guid isPermaLink="false">https://medium.com/p/cbd72c40c192</guid>
            <dc:creator><![CDATA[David Campey]]></dc:creator>
            <pubDate>Mon, 16 Nov 2020 14:06:00 GMT</pubDate>
            <atom:updated>2020-11-16T14:06:00.124Z</atom:updated>
            <content:encoded><![CDATA[<p>Out on the sea, there is a strange paradox that often plays out. You’ll see a salty old sea captain, hands flopped over the wheel, sailing along quite relaxed. Meanwhile, in the boat next to him a young crew are swarming all over, steering to correct the line, adjusting this, tweaking that, maximizing the wind power.</p><p>But the old timer is going faster.</p><p>Why? Because, you see, the rudder creates resistance.</p><p>Under the surface, every time we try to correct the boat, we are adding resistance in the act of steering. Constant adjustments causes more turbulence than the minor benefit of slight optimization in laminar flow.</p><p>This story was shared with me as a leadership metaphor by my friend <a href="http://www.medium.com/@rogernort">Roger Norton</a>, who has actually sailed around the world, a few times (by distance).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bfGXtAThfq-BEItKgk7ebw.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@thommilkovic?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Thom Milkovic</a> on <a href="https://unsplash.com/s/photos/sailing-race?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><h4>What does this mean for my leadership?</h4><p>When as a leader I make too many course corrections, “just” pointing out a few minor things, it creates resistance and turbulence. It can throw off the groove of a team and create a response in the opposite direction, instead of generating momentum.</p><p>Instead, I try to reflect on if correcting it now is going to create resistance or if we might leave it for now to generate momentum. It might be better to see where we end up and then maybe have a single larger course correction.</p><h4>Isn’t that counter to “Agile”?</h4><p>Not really. Agile methods are designed to facilitate responding to change. A healthy system facilitates this flow, taking times of reflection &amp; review for steering at appropriate moments.</p><p><em>Inspect and adapt</em> is important, but we don’t want too much inspection and too much adaption, especially external adaption.</p><p><em>Responding to change over sticking to a plan</em> is likewise an important value prioritization, but allowing things to run their course, pick up speed, and then picking an appropriate time and place to respond to the change is the art.</p><blockquote>“If you try to change it, you will ruin it. Try to hold it, and you will lose it.”<br>― <strong>Lao Tzu, </strong><a href="https://www.goodreads.com/work/quotes/100074"><strong>Tao Te Ching</strong></a></blockquote><p>Wait, isn’t this just veiled passive aggression? You are missing acting on impulses to correct, and this avoiding conflict, right? It can be, if you never have the opportunity to course correct, but if you introduce a cadence of reflection when feedback is desired, then it can be heard and acted on without creating inappropriate resistance and turbulence.</p><h4>So, what now?</h4><p>It might start by holding the thought that “the rudder creates resistance” and trying to bring an active awareness to when and how we course correct. Or maybe flop your hands on the wheel, go with the flow, and keep a weather eye for an opportune moment to adjust.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cbd72c40c192" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A dog barking in a village…]]></title>
            <link>https://medium.com/@davidcampey/a-dog-barking-in-a-village-11e1fcfff911?source=rss-210438420dbd------2</link>
            <guid isPermaLink="false">https://medium.com/p/11e1fcfff911</guid>
            <category><![CDATA[emotions]]></category>
            <category><![CDATA[anger]]></category>
            <category><![CDATA[personal-growth]]></category>
            <category><![CDATA[emotional-intelligence]]></category>
            <category><![CDATA[psychology]]></category>
            <dc:creator><![CDATA[David Campey]]></dc:creator>
            <pubDate>Mon, 25 May 2020 17:36:23 GMT</pubDate>
            <atom:updated>2020-05-25T17:36:23.011Z</atom:updated>
            <content:encoded><![CDATA[<p>Imagine a village.</p><p>A village lying dark and quiet in the cool moonlight. A night, like any other. Villagers warm in their beds. All the terrors of the night far away.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*SHSHf_7weYdwipPdDstuZg.jpeg" /><figcaption><a href="http://www.cassiopeiaart.com/uploads/village_roof_tops.jpg">Village Roof Tops</a> by <em>Cathrine Langwagen </em><a href="http://www.cassiopeiaart.com/"><em>http://www.cassiopeiaart.com/</em></a></figcaption></figure><p>Somewhere, a dog begins to bark.</p><p>It startles some of the sleeping villagers.</p><p>“What? Oh? <em>That </em>dog barking again.” “Can we ignore it?” “Maybe it’s nothing, just a cat?”</p><p>A candle flame flickers to life in a window. But not really worth doing anything yet. “Will it go away?”</p><p>Another dog wakes up. More agitation sharpening this bark.</p><p>The mayor sighs in his chambers, “Could it be a real something? Then again, no, probably not.” He stuffs his ear full of feather pillow, trying to muffle the noise and get some sleep. “There’s probably nothing I can do, anyway”.</p><p>Dogs are barking across the village. Some now barking at other dogs, as they do. Others sounding more and more alarmed.</p><p>“If I just stay quiet… the dogs might calm themselves.”</p><p>A window cracks open to the cold night air and someone yells out at the dogs and the darkness. The dogs quiet down. “Better. Such a nuisance, why do we even have these dogs?”</p><p>They start up again.</p><p>“Could it be that something is actually there? Somethings?” That thought sends the mayor snuggling deeper under the covers. “Can’t it just go away?”</p><p>A snarl. More dogs, closer now. “What now?!?”</p><p>The mayor gives in and hazards a safe glance out through his unlighted window, what is it that they’re barking at? A glimmer of steel in the moonlight falling on the town square, undeniably a something.</p><p>“Invaders are out there, and they, they… are in my town.”</p><p>Dogs barking, everywhere now.</p><p>“Definitely should do something now. But… I can’t think for all these damn dogs!”</p><p>Slip out of bed, pull on a coat and boots, pick up a staff from the fireplace…</p><p>… and then…</p><p>Try a dash towards the back door, “Maybe I could get away and have a chance to… just… think a little!”</p><p>The shadow looming at the back door removes that option.</p><p>Trapped.</p><p>It’s finally enough, it’s now or never. “The enemy!” the mayor snarls. Kicking open the door and wildly swinging his staff he hurtles into the darkness.</p><p>Meanwhile, in another dimension, your poor colleague looks on bewildered as you snap, “What?! No, I don’t want a damn cup of tea, can’t you see I’m… aaargh!”</p><h4>Wait, what?</h4><p>This is a metaphor for anger from <a href="https://abrandtherapy.com/">Andrea Brandt</a>’s writing on passive aggression.</p><ul><li>The village is a mind. A peaceful mind. The edges of the village are the mind’s boundaries.</li><li>The intruder is something that crosses our boundaries.</li><li>The dogs barking are signals of anger, signalling that something is crossing those boundaries.</li><li>The mayor is the conscious mind.</li></ul><p>It isn’t always clear what the dogs are barking at, they alarm the village and the mayor.</p><p>Our anger signals us, the dogs start barking. With it comes a need to address the anger to “go and see”, to calm the dog.</p><p>If the energy from this impulse is not used, it carries over, the dog keeps barking. The dogs could even wake other dogs.</p><p>The longer the intruder stays and tramples around inside the village the more dogs it wakes.</p><h4>Withholding and Dumping</h4><p>If we can’t find a healthy way to use our anger, the energy stores up and drives us to one of the two dysfunctions: anger withholding, or anger dumping.</p><p>In <strong>Withholding</strong>, we essentially snuggle deeper into the bed, maybe getting up to ensure that the door is locked. We avoid and definitely don’t act on the anger, trying not to even mention it.</p><p>In <strong>Dumping</strong>, the mayor finally flies off the handle. The anger brewing inside finally moves us to action which is often uncontrolled, unproductive and destructive.</p><p>In between the two is a <em>path of mindful anger</em> that lets us go and see what the dogs are barking at. Then we can meet the intruder, friend or foe, and point out the boundaries they have crossed. Pat the dog, go back to bed.</p><p>Finding that middle path is a challenge, hopefully this metaphor helps.</p><p>For more, check out Andrea’s <a href="https://abrandtherapy.com/blog/#anger">blog posts on anger</a>, or maybe one of <a href="https://www.amazon.com/Andrea-Brandt/e/B00EABHG7K">her books</a>, I found both books dealing with anger to be great reads.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=11e1fcfff911" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[HowTo: pip install eo-learn on windows]]></title>
            <link>https://medium.com/@davidcampey/howto-pip-install-eo-learn-on-windows-a76a6498802c?source=rss-210438420dbd------2</link>
            <guid isPermaLink="false">https://medium.com/p/a76a6498802c</guid>
            <category><![CDATA[eo-learn]]></category>
            <category><![CDATA[python]]></category>
            <category><![CDATA[gis]]></category>
            <category><![CDATA[pip]]></category>
            <dc:creator><![CDATA[David Campey]]></dc:creator>
            <pubDate>Tue, 22 Jan 2019 11:30:25 GMT</pubDate>
            <atom:updated>2019-01-25T09:19:26.547Z</atom:updated>
            <content:encoded><![CDATA[<p>I’ve spent some time trying to execute pip3 install eo-learn on Windows 10, with python 3.7.</p><p>It isn’t easy currently, but it is possible with help from friends.</p><p>Start with python 3.7 <strong>64-bit</strong>, downloaded from: <a href="https://www.python.org/downloads/release/python-372/">https://www.python.org/downloads/release/python-372/</a></p><p>My preference is to install for all users (hidden inside advanced install options) so that it goes into c:\Program Files\Python37. I find this more convenient than having it deep inside my user directory.</p><p>Then for convenience check that C:\Program Files\Python37\and C:\Program Files\Python37\Scripts are in your path.</p><p>Then, simply run:</p><pre>pip3 install eo-learn</pre><p>See the errors below and follow along my journey, your mileage may vary.</p><h4>pip error installing rasterio (#1)</h4><pre>ERROR: Numpy and its headers are required to run setup()</pre><p>Okay, this one is easy: pip3 install numpy</p><h4>pip error on rasterio (#2)</h4><pre>ERROR: A GDAL API version must be specified. Provide a path to gdal-config using a GDAL_CONFIG environment variable or use a GDAL_VERSION environment variable.</pre><p>For pippy goodness, install using a wheel from <a href="https://www.lfd.uci.edu/~gohlke/pythonlibs/#gdal">https://www.lfd.uci.edu/~gohlke/pythonlibs/#gdal</a> (via <a href="https://gis.stackexchange.com/a/7617/135609">https://gis.stackexchange.com/a/7617/135609</a>) installed using a line like:</p><pre>pip3 install C:\Users\David\Downloads\GDAL-2.3.3-cp37-cp37m-win_amd64.whl</pre><p>(First time round, I had installed GDAL with a Windows installer (e.g. from <a href="http://trac.osgeo.org/osgeo4w/wiki">http://trac.osgeo.org/osgeo4w/wiki</a>) for a previous piece of work)</p><p>Once you have GDAL installed, make a BAT file e.g. c:\bin\gdal-config.bat with the following contents</p><pre>@echo off</pre><pre>set OPTION=%1</pre><pre>IF &quot;%OPTION%&quot;==&quot;--cflags&quot; (<br>echo -I_&lt;path to GDAL include directory&gt;<br>) ELSE IF &quot;%OPTION%&quot;==&quot;--libs&quot; (<br>echo -L_&lt;path to GDAL lib directory&gt;_ -lgdal_i<br>) ELSE IF &quot;%OPTION%&quot;==&quot;--datadir&quot; (<br>echo &lt;path to GDAL data directory (%GDAL_DATA% if you&#39;re using OSGeo4W)&gt;<br>) ELSE IF &quot;%OPTION%&quot;==&quot;--version&quot; (<br>echo &lt;GDAL version (e.g. 2.1.0)&gt;<br>)</pre><p>(wizardry via achamberlain on<br>https://github.com/Toblerity/Fiona/issues/364#issuecomment-229037415)</p><p>Then set the GDAL_CONFIGappropriately.</p><pre>set GDAL_CONFIG=”C:\bin\gdal-config.bat”</pre><p>You may also need to set the GDAL_VERSION like this:</p><pre>gdalinfo --version<br>set GDAL_VERSION=[version from gdalinfo]</pre><p>If you installed with the wheel, gdalinfo is hidden in “C:\Program Files\Python37\Lib\site-packages\osgeo\gdalinfo”</p><p>C:\WINDOWS\system32&gt;set GDAL_VERSION=2.3.3</p><p>If all goes well, you should be through that and run into…</p><h4>pip error installing shapely</h4><pre>OSError: [WinError 193] %1 is not a valid Win32 application</pre><p>To get past this one, get the appropriate wheel (e.g. -cp37-cp37m-amd64.whlfor CPython 3.7, 64-bit) from <a href="https://www.lfd.uci.edu/~gohlke/pythonlibs/#shapely">https://www.lfd.uci.edu/~gohlke/pythonlibs/#shapely</a> and install:</p><pre>pip3 install C:\Users\David\Downloads\Shapely-1.6.4.post1-cp37-cp37m-win_amd64.whl</pre><p>Then running pip again you should see</p><pre>pip3 install eo-learn<br>...<br>Requirement already satisfied: shapely<br>...</pre><p>Woohoo!</p><h4>LightGBM needs 64-bit python</h4><pre>Exception: Cannot install LightGBM in 32-bit Python, please use 64-bit Python instead.</pre><p>Unfortunately, the default python download I had installed was 32-bit, so back to the beginning for me. Hopefully you read that bit in the preamble, otherwise, back to the beginning for you too :)</p><h4>pip error installing fiona</h4><pre>error: command &#39;cl.exe&#39; failed: No such file or directory</pre><p>I suggest you don’t try to get the build to work here, just use a pre-built wheel from <a href="https://www.lfd.uci.edu/~gohlke/pythonlibs/#fiona">https://www.lfd.uci.edu/~gohlke/pythonlibs/#fiona</a>, installed with:</p><pre>pip install C:\Users\David\Downloads\Fiona-1.8.4-cp37-cp37m-win_amd64.whl</pre><p>(thanks to <a href="https://github.com/Toblerity/Fiona/issues/449#issuecomment-304318720">https://github.com/Toblerity/Fiona/issues/449#issuecomment-304318720</a> and <a href="https://github.com/Toblerity/Fiona/issues/449#issuecomment-439653175">https://github.com/Toblerity/Fiona/issues/449#issuecomment-439653175</a> for the pointers)</p><h4>rasterio setup.py error</h4><pre>rasterio/_base.c(605): fatal error C1083: Cannot open include file: ‘cpl_conv.h’: No such file or directory</pre><p>Again, grab the wheel from <a href="https://www.lfd.uci.edu/~gohlke/pythonlibs/#rasterio">https://www.lfd.uci.edu/~gohlke/pythonlibs/#rasterio</a> and install like so:</p><pre>pip install C:\Users\David\Downloads\rasterio-1.0.13-cp37-cp37m-win_amd64.whl</pre><h3>and then eo-learn installed!</h3><p>Hope this worked for you, if it did, well done! :David</p><h4>— APPENDIX: pip install fiona —</h4><p>If you’re not trying to get fiona to build from pip, you really don’t need this bit, just use the WHL!</p><p>I’m just leaving it here in case it helps guide someone into the right direction.</p><pre>error: command &#39;cl.exe&#39; failed: No such file or directory</pre><p>Okay, for this you’ll need to install the MS Build tools, then add the folder ending in \Hostx64\x64 with CL.exe in it to your path, e.g.</p><pre>set path=%path%;c:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\VC\Tools\MSVC\14.16.27023\bin\Hostx64\x64</pre><p>(Note: if you use e.g. \Hostx64\x86 you will run into c1: fatal error C1356: unable to find mspdbcore.dll)</p><p>Then you’ll run into</p><pre>C:\Program Files (x86)\Windows Kits\10\include\10.0.17763.0\ucrt\corecrt.h(10): fatal error C1083: Cannot open include file: &#39;vcruntime.h&#39;: No such file or directory<br>    error: command &#39;c:\\Program Files (x86)\\Microsoft Visual Studio\\2017\\BuildTools\\VC\\Tools\\MSVC\\14.16.27023\\bin\\Hostx64\\x64\\cl.exe&#39; failed with exit status 2</pre><p>Which can properly be sorted out by running vcvars64.bat (via h<a href="https://stackoverflow.com/a/44133043/74708">ttps://stackoverflow.com/a/44133043/74708</a>).</p><p>This gave me the error</p><pre>“\Microsoft was unexpected at this time.” </pre><p>which it turns out was because the registry key</p><pre>&quot;HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SDKs\Windows\CurrentInstallFolder&quot;</pre><p>Was incorrectly set, setting the correct location (“C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A” for me) will move you onto this error:</p><pre>fiona/schema.c(589): fatal error C1083: Cannot open include file: &#39;gdal.h&#39;: No such file or directory</pre><p>I then gave up when I found the pre-built whl.</p><p><strong>— END APPENDIX: pip install fiona —</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a76a6498802c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Learning not to interrupt]]></title>
            <link>https://medium.com/@davidcampey/learning-not-to-interrupt-6da438e4e773?source=rss-210438420dbd------2</link>
            <guid isPermaLink="false">https://medium.com/p/6da438e4e773</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[life-lessons]]></category>
            <category><![CDATA[self-improvement]]></category>
            <category><![CDATA[conversations]]></category>
            <dc:creator><![CDATA[David Campey]]></dc:creator>
            <pubDate>Fri, 17 Mar 2017 12:09:38 GMT</pubDate>
            <atom:updated>2017-03-17T12:09:38.191Z</atom:updated>
            <cc:license>http://creativecommons.org/licenses/by/4.0/</cc:license>
            <content:encoded><![CDATA[<p>Interrupting breaks our conversations.</p><p>Some of my most valued colleagues have, over the years, called me out for interrupting (as well as talking too much).</p><p>The result is that people don’t feel heard.</p><blockquote>“You’re used to being the smartest person in the room, you need to realise that the others here are smart too.” <br>Colleen Barrell (to me, at Microsoft, 2008)</blockquote><p>This is not a new problem for me.</p><p>I have been reflecting on this.</p><p>In this post I’ll share some of the lovely insights I’ve come across from wonderful people.</p><h3>Conversational Styles</h3><p>I’ve come to realise there are multiple conversational styles, some people don’t like being interrupted and some don’t mind it.</p><p>I usually justify my style by saying that I started my business with a co-founder who also loved the talking-over-each-other passionate debate, so I have a deeply ingrained conversational culture of interrupting.</p><p>While prepping for a recent DroneClouds.com trip to visit Airbus DS in Toulouse I came across validation in this insight offered to people doing business in France.</p><blockquote>It is not frowned upon in France to ask a lot of questions and to interrupt somebody before they have finished. It is a common French conversation style. In other countries, interrupting may be inappropriate but in France it is simply a way to express your interest in the other person and the conversation.</blockquote><blockquote>If you are being interrupted, take it initially as a positive sign that they like what you’re saying. Reciprocally, if you want to show your interest, don’t be afraid to interrupt and finish other people’s sentences, too.</blockquote><blockquote><a href="http://www.thelocal.fr/20130304/top-ten---french-business-etiquette">Ten tips on French business etiquette — thelocal.fr</a></blockquote><p>Realising that in some places it is a common style made me feel better about myself.</p><p>But: this justification and excuse isn’t really satisfactory, because that style may have been harming my interactions and ability to have meaningful, effective conversation.</p><h3>Responsibility</h3><p>After learning about Christopher Avery’s responsibility framework, it became clear that, by getting stuck justifying, I was in a non-responsive state, unable to take the appropriate response and inspect &amp; adapt my behaviour.</p><p>For a better summary of the responsibility process than I could ever give, watch Christopher Avery himself explaining it in this 7 minute video.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F-T3IZ2ISxag%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D-T3IZ2ISxag&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F-T3IZ2ISxag%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/4ab4bc22b59bb3f5c7c7846a3af5a991/href">https://medium.com/media/4ab4bc22b59bb3f5c7c7846a3af5a991/href</a></iframe><p>At another level, looking at interrupting itself in the responsibility framework lens: much of our interrupting and over-talking stems from our brain’s coping mechanisms kicking — which means we can’t take the appropriate response.</p><p>This cultivated a desire to be more responsible in both my approach to the problem and in my conversational style.</p><h3>Wait vs Interrupt</h3><p>Evaluating the different approaches, I got an interesting insight from <a href="http://lesswrong.com/lw/j5n/wait_vs_interrupt_culture/">Wait vs Interrupt Culture</a>, a great piece by Benquo over at lesswrong.com.</p><p>It covers how talking school facilitators at St John’s College help to change the flow of the conversation and the beneficial effects of waiting rather than interrupting.</p><blockquote>If talking at all is an implied claim that what you’re saying is the most important thing that can be said, then polite people keep it short.</blockquote><blockquote><a href="http://lesswrong.com/lw/j5n/wait_vs_interrupt_culture/">Wait vs Interrupt Culture</a>, Benquo, lesswrong.com</blockquote><p>This point, that being listened to creates shorter statements and more effective conversations, is a clear advantage of the non-interrupting, wait style.</p><h3>Listening <strong>≠Agreement</strong></h3><p>Lyssa Adkins is a coach of agile coaches and all round wonderful human.</p><p>In a recent piece of Inspiration for Agile Coaches, she shares the notion that listening is not equal to agreement.</p><blockquote>Folks, we gotta start helping people pull apart the notion that listening equals agreement. Listening and agreement are two separate things and two separate steps in a conversation. Here’s how it goes: Listen first to understand the other. Then, agree or not.</blockquote><blockquote>Maybe you will see this play out this week with a team member or manager who muscles out another’s idea by talking over the other person, or maybe this will play out with your very own family at the dinner table.</blockquote><blockquote><a href="https://t.e2ma.net/message/jfxhj/jnjwf">Inspiration for Agile Coaches, Lyssa Adkins</a></blockquote><p>This was pretty useful to me as it helped me to articulate that the reason I was often interrupting was to “put things right” or correct something someone else was saying (or add my $.02 to also feel valuable).</p><p>Being able to listen, understand then respond in agreement or disagreement lets the conversation flow.</p><h3>Ayumi ashi, irimi, tenkan</h3><p>I’ve spent the last 17 years on and off the mat learning the flow of Aikido. In my reflections on listening, I’ve realised the way of peace in Aikido points the way to the same listening insights.</p><blockquote>Ayumi Ashi, <br>irimi, <br>tenkan.</blockquote><blockquote>Step off the line of conflict, <br>enter close to the other, <br>turn with the other.</blockquote><blockquote>Saud Anderson, Mushindo Aikido, Cape Town</blockquote><p>Or, in a conversation:</p><p>Don’t interrupt<br>Listen to what they’re saying<br>Respond appropriately</p><p>In Aikido, as in an effective conversation, our goal is to harmoniously flow with conflict and attain the best outcome for both.</p><h3>“A” list needs</h3><p>In <a href="https://www.amazon.com/Mindful-Anger-Pathway-Emotional-Freedom/dp/0393708942">Mindful Anger: A Pathway to Emotional Freedom</a>, Andrea Brandt shares that anger gives us a positive energy to resolve conflicts. These conflicts arise as our minds trigger defense of our boundaries to ensure our needs are met.</p><p>We have many needs, in Andrea’s book, she shares a list of emotional needs, the “A” list: Accessibility, Attention, Affection, Appreciation, Acceptance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kWDdLOnumJBIA8DGMiL3mg.jpeg" /><figcaption>“A” list up on our chalkboard at Afrolabs</figcaption></figure><p>Andrea follows this list with the statement that if these needs are met, the result is <em>engagement</em>. A simple path of needs that lead to that mystical thing that eludes most business cultures is laid out here, tantalisingly within reach.</p><p>Reflecting on interruption from the perspective of these needs, it seems clear to me that interruption can deny people these needs.</p><p>Specifically: interrupting people is not Accepting people’s point of view; <br>is not giving them full Attention as you are focused on your own statements;<br>reduces your Accessibility to them as they feel they can’t get through to you;<br>and masks any Appreciation or Affection you may feel towards them for their completely valid point of view.</p><p>Denying people these needs by interrupting them creates frustration, anger, disappointment… and results in <em>disengagement</em>.</p><h3>Developing the skills</h3><p>These insights can help build a desire, hopefully they have.</p><p>Ultimately the path to change requires work on yourself, I for one am resolved more than ever to work on developing my skills of listening and trying to interrupt less.</p><p>If you’re also growing this desire, here are three action steps you could try today.</p><h4>Something to try: Switch Experimentally</h4><p>It can be a big thing to switch styles, why not try it experimentally.</p><blockquote>So if you’re only used to one style, see if you can try out the other somewhere. Or at least pay attention and see whether you’re talking to someone who follows the other norm. And don’t assume that you know which norm is the “right” one; try it the “wrong” way and maybe you’ll learn something.</blockquote><blockquote><a href="http://lesswrong.com/lw/j5n/wait_vs_interrupt_culture/">Wait vs Interrupt Culture</a>, Benquo, lesswrong.com</blockquote><h4>Something to try: Chess Timer</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/180/1*ccrggW-YgnbN6KxHJfIQQQ.jpeg" /><figcaption><a href="https://play.google.com/store/apps/details?id=com.chess.clock&amp;hl=en">Android Chess Clock</a></figcaption></figure><p>Being a geek, I’ve even tried using a chess timer to balance the amount of time each person speaks and to make interruption explicit.</p><p>This has actually worked for me, much to the amusement of my colleague.</p><h4>Something to try: Watch “A courageous choice”</h4><p>Finally, if you’re thirsting for more listening, I’ll leave you with this wonderful keynote “<a href="https://www.infoq.com/presentations/agile-courageous-choice">Agile: A courageous choice</a>” by Olaf Lewitz.</p><p>It’s an hour full of listening goodness. I’ve watched it twice over the past year — it’s had me enraptured and un-interrupting.</p><p><a href="https://www.infoq.com/presentations/agile-courageous-choice">Agile - A Courageous Choice</a></p><h3>Thanks for “listening”</h3><p>I hope you’ve enjoyed some insight into my learnings so far, thanks for “listening” and reading this far. Hopefully sharing this will help improve our conversational cultures.</p><p>Good luck listening!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6da438e4e773" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>