<?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 Will Sewell on Medium]]></title>
        <description><![CDATA[Stories by Will Sewell on Medium]]></description>
        <link>https://medium.com/@willsewell_?source=rss-1c93f425c139------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*5xkZMeoF_UZObFJ0QUvxuA@2x.jpeg</url>
            <title>Stories by Will Sewell on Medium</title>
            <link>https://medium.com/@willsewell_?source=rss-1c93f425c139------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 05:13:07 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@willsewell_/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[Notes from The Lead Developer UK conference]]></title>
            <link>https://medium.com/pusher-app/notes-from-the-lead-developer-uk-conference-4c46c990b636?source=rss-1c93f425c139------2</link>
            <guid isPermaLink="false">https://medium.com/p/4c46c990b636</guid>
            <category><![CDATA[thought-leadership]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[developer]]></category>
            <category><![CDATA[conference]]></category>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[Will Sewell]]></dc:creator>
            <pubDate>Tue, 27 Jun 2017 09:21:50 GMT</pubDate>
            <atom:updated>2017-11-22T15:03:50.073Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*f0wSwO1m5oGBHfRJlbKyyw.jpeg" /></figure><p>Just over a week ago, some of the engineering team at <a href="https://pusher.com/">Pusher</a> headed to <a href="http://2017.theleaddeveloper.com/">The Leader Developer UK</a> conference. It was my first time at a “soft skills” conference; lot’s more opinions rather than facts. I didn’t agree with everything, but I found it a great opportunity to reflect on the way I act and the relevance of the talk content to my experience.</p><p>I was taking notes during the conference. The team at Pusher found them interesting, so why not share them with the world? It’s essentially a summary of the talks that resonated with me, interspersed with some of my own opinions.</p><h3>Patrick Kua: The Constant Life of a Tech Lead</h3><p><a href="http://2017.theleaddeveloper.com/talks#patrick-kua">http://2017.theleaddeveloper.com/talks#patrick-kua</a></p><p>This was a well presented talk from Patrick Kua of <a href="https://www.thoughtworks.com/">ThoughtWorks</a>, giving a summary of some skills required of tech leads.</p><p>It was interesting to hear Patrick bringing up the idea of different types of people who are suited to different parts of a project lifecycle: <a href="http://blog.gardeviance.org/2015/03/on-pioneers-settlers-town-planners-and.html">pioneers, settlers, town planners</a>. This is an idea that is popular at <a href="https://pusher.com/">Pusher</a>. I like the concept; my concern is that it is easy for people to become pigeon-holed in a managers eyes and it might be hard to change perceptions later on if we stick to these boxes too rigidly.</p><p>Which are you?</p><p>Later on in the talk he want on to emphasise the importance of time management. This is something that is becoming more relevant to me as my calendar gets fuller!</p><blockquote>I have two kinds of problems, the urgent and the important. The urgent are not important, and the important are never urgent.</blockquote><blockquote>— Dwight D. Eisenhower</blockquote><p>He mentioned the <a href="https://en.wikipedia.org/wiki/Time_management#The_Eisenhower_Method">Eisenhower matrix</a> as a technique for categorising tasks, and focusing on the highest priority.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*D6kSyx_dC-vX0t16.gif" /><figcaption>Source: <a href="http://joshmedeski.com/eisenhower-matrix-todoist/">http://joshmedeski.com/eisenhower-matrix-todoist/</a></figcaption></figure><p>Finally, I liked how Patrick advocated for <a href="https://en.wikipedia.org/wiki/Double-loop_learning">double-loop learning</a>. It’s easy to end up repeatedly trying to solve a problem in a similar way, when it might be more effective to take a step back and rethink the mental model/problem itself before tackling it again.</p><h3>Adrian Howard: How to Talk to Earthlings?</h3><p><a href="http://2017.theleaddeveloper.com/talks#adrian-howard">http://2017.theleaddeveloper.com/talks#adrian-howard</a></p><p>My big takeaway: be conscious of active listening. Adrian made a point that through our lives we are socialised in a conversation to listen for an interesting point, at which point we spend the remaining time the other person is speaking waiting for a pause so we can say our interesting point.</p><p>This might be OK in some social/group settings, but in deeper conversations with reportees, it is important to focus on what they are saying and not spend time formulating a response in your head. It’s ok if there are pauses. Be conscious about listening.</p><p>A good response is of the form “tell me more about X… “ where X is something they have said to show that you have taken it in.</p><p>He also made the point that people tend to be unsure about what they really want (and might try and give you the answer <em>you</em> want). It’s good to ask for stories rather than abstract questions. Focus on how they would react in specific situations.</p><h3>Katherine Wu: Ask vs. Guess Culture Communication</h3><p><a href="http://2017.theleaddeveloper.com/talks#katherine-wu">http://2017.theleaddeveloper.com/talks#katherine-wu</a></p><p>Katherine argued that there is a spectrum of cultures/people. From the “ask” people (assertive and thick-skinned), to “guess” people (polite and find it hard to say no). The main point was that both are normal and have advantages/disadvantages, but it’s important to be conscious of the differences. This is particularly true if you are more “ask” and are not used to picking up on the subtler ways “guess” people have of asking for things. It’s also important to be aware the “guess” people might not voluntarily bring things up that are important, or might be pressured into saying “yes”; you can preface questions with “it’s ok to say no…”. It might be worth getting feedback from someone who is not like you (e.g. an “ask” if you are a “guess”) before pressing send on an important email.</p><p>The concept seems to have come from this MetaFilter comment: <a href="http://ask.metafilter.com/55153/Whats-the-middle-ground-between-FU-and-Welcome#830421">http://ask.metafilter.com/55153/Whats-the-middle-ground-between-FU-and-Welcome#830421</a> and seems to have resonated with a lot of people’s experience (it did for me).</p><h3>Maria Gutierrez: Time to Focus on Your Goals</h3><p>This talk might be interesting to you have you want to improve long term goal planning/time management. Some recommendations:</p><ul><li>Book a day out of the year to plan/priorities long term goals/career trajectory</li><li>Aim to develop a mixture of skills: some technical, some to do with management, some that you are already good at, some that are new</li><li>After each day, write down anything you have learned. Whenever I do this, it makes me far more conscious about my learning</li></ul><p>I liked this talk, not because I completely agreed with everything, but because I tend to easily get bogged down in the nitty/gritty day-to-day and not reflect on these more important things enough.</p><h3>Erika Carlson: Better: Fearless Feedback for Software Teams</h3><p><a href="http://2017.theleaddeveloper.com/talks#erika-carlson">http://2017.theleaddeveloper.com/talks#erika-carlson</a></p><p>General tips on giving feedback.</p><ul><li>Feedback (including constructive) is great and I don’t think we do enough of this</li><li>If you are giving feedback, be upfront about the agenda before booking it in. People can easily assume the worst and become anxious.</li><li>Repeat back your understanding of what someone has said in a 1 on 1.</li><li>This was actually in Randall Koutnik’s talk later on, but it’s more relevant here. Randall mentioned how, after giving constructive feedback, you should also offer to play an active role in their development going forward. I can see how this would encourage responsibility for the feedback that one gives.</li></ul><p>On a point Erika made unrelated to feedback: delegate as many decisions as possible, but make sure you provide the necessary business context in order for those decisions to be made.</p><p>There was a bunch of other good recommendations in <a href="https://www.slideshare.net/ErikaCarlson4/better-fearless-feedback-for-software-teams">the slides</a> if you want more information.</p><h3>Nickolas Means: The Original Skunk Works</h3><p><a href="http://2017.theleaddeveloper.com/talks#nickolas-means">http://2017.theleaddeveloper.com/talks#nickolas-means</a></p><p>This was the most enjoyable talk for me. A very well told story on the history of how the <a href="http://www.lockheedmartin.co.uk/us/aeronautics/skunkworks.html">Skunk Works</a> team at Lockheed designed a series of incredible fighter jets. The team was a small R&amp;D team which rapidly developed new “products”. It was particularly interesting hearing about some of the design trade-offs they made: planes with a single landing gear; leaking fuel tanks; insufficient power to start its own engines; insufficient fuel capacity. The point being that it didn’t matter because they still solved their main business objective.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*Es5Mqy7zFmuxnvhl.gif" /><figcaption><em>An SR-71 Blackbird leaking fuel on the runway — source: </em><a href="https://flic.kr/p/7dURC">https://flic.kr/p/7dURC</a></figcaption></figure><p>I highly recommend watching a recording of this talk if it sounds interesting.</p><h3>Mathias Meyer: Building and Scaling a Distributed and Inclusive Team</h3><p><a href="http://2017.theleaddeveloper.com/talks#mathias-meyer">http://2017.theleaddeveloper.com/talks#mathias-meyer</a></p><p>A talk going into <a href="https://travis-ci.org/">TravisCI</a>’s experience with managing a remote team. I’m always interested in hearing people’s experience in remote teams because there’s quite a few obvious benefits (to the business, not to mention the flexibility for employees): increased diversity; closeness to customers; people on-call in all timezones. The downsides feel less concrete to me: feeling less part of a team; silos forming; lower information bandwidth, etc. I like to hear people’s actual experience with these problems, and how they combat them.</p><ul><li>Apparently all discussion at Travis happens over GitHub issues. I can imagine this being frustratingly slow for some discussions, but I thought it was a great idea for his particular example: deciding on the company’s values. This is the kind of discussion that I think is much better suited to asynchronous communication where people have the time to think, and only those who are interested need to participate.</li><li>With more written down, you get decision logs for free. Something which I don’t think I do enough of.</li><li>Chatops used heavily (more transparency)</li><li>Culture of jumping into video calls during incident</li></ul><p>He mentioned the downsides of remote work, but did not go into them as much as I hoped.</p><h3>Sabrina Leandro: Big Rewrite Strikes Again</h3><p><a href="http://2017.theleaddeveloper.com/talks#sabrina-leandro">http://2017.theleaddeveloper.com/talks#sabrina-leandro</a></p><p>Sabrina’s central point was that you shouldn’t rewrite the whole system at once for two reasons: it’s risky (more unknowns with the whole system), and no value is created until the entire rewrite is finished. Basically recommended adopting the <a href="https://www.martinfowler.com/bliki/StranglerApplication.html">Strangler</a> approach to rewriting. This approach is what we have adopted at <a href="https://pusher.com/">Pusher</a> and I think it’s a great idea.</p><p>Sabrina made a couple of other interesting points:</p><ul><li>A rewrite is also a time to cut out <em>product features</em> which did not turn out to be as successful as the hypothesis. People often forget this and try and achieve complete feature parity with a re-write.</li><li>Rewrites can be daunting and take some time. At <a href="http://www.songkick.com/">Songkick</a> they created a gamification system to add a feeling a progress and achievement to a rewrite that took 2 years. Could be a fun/effective motivator. Some of the “achievements” were quite entertaining. You’d have to check <a href="https://speakerdeck.com/saleandro/big-rewrite-strikes-again-lead-dev-london-2017">the talk slides</a> to see these.</li></ul><h3>Randall Koutnik: Implementers, Solvers, and Finders: Rethinking the Developer Career Path</h3><p><a href="http://2017.theleaddeveloper.com/talks#randall-koutnik">http://2017.theleaddeveloper.com/talks#randall-koutnik</a></p><p>Randall proposed a model for career levels:</p><ol><li>Problem implementor — takes a solution to a problem and gets it implemented</li><li>Problem solver — takes a problem and recursively break it down into sub-problems/solutions</li><li>Problem finder — uses business context to generate new problems that are valuable to solve</li></ol><p>This categorisation resonated with us. It’s tricky to get the incentives right if career progression is too specific. I thought the model the Randall proposed had a nice mix of being general, while capturing the important differences between each level. I recommend <a href="https://speakerdeck.com/rkoutnik/implementers-solvers-finders-rethinking-the-developer-career-path">the slides</a>/watching the talk for more detail on the distinction between each of them.</p><p>He also stressed the importance of having the right balance of experience levels in a team. e.g. too many problem finders and the are lots of ideas, but nothing actually gets done.</p><h3>Lara Hogan: Leading by Speaking</h3><p><a href="http://2017.theleaddeveloper.com/talks#lara-hogan">http://2017.theleaddeveloper.com/talks#lara-hogan</a></p><p>Lot’s of great public speaking tips:</p><ul><li>Make a single point</li><li>Two types of structure: 1. open with a thesis and spend the rest of the talk providing supporting arguments, or 2. tell a story</li><li><a href="https://speakerdeck.com/lara/demystifying-public-speaking">Lara’s slides</a> give a more detailed overview of a good structure</li><li>Tell mini stories if the content is dry (I’m personally not convinced by this. There’s very little content I find dry; if it is, it’s usually due to the delivery)</li><li>Practice with a small group of people who are good at giving feedback</li><li>Ask beforehand the kind of feedback you are interested in (avoids “it was good” responses)</li><li>Feedback should be <em>specific</em> and <em>actionable</em></li><li>Ask for weird/surprising practice questions</li><li>Power pose! (<a href="https://www.ted.com/talks/amy_cuddy_your_body_language_shapes_who_you_are">no, really</a>)</li></ul><p>By the end of the conference I think we were all pretty exhausted from everything we’d heard. It was a single-track conference with up to 12 talks per day (!), so it was borderline information-overload, but I’m thoroughly pleased I went.</p><p>If you’re looking to move into more of a leadership role in a tech team, then I recommend checking out the recordings once they become available and attending next year!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4c46c990b636" width="1" height="1" alt=""><hr><p><a href="https://medium.com/pusher-app/notes-from-the-lead-developer-uk-conference-4c46c990b636">Notes from The Lead Developer UK conference</a> was originally published in <a href="https://medium.com/pusher-app">Pusher</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>