<?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 Tito Sarrionandia on Medium]]></title>
        <description><![CDATA[Stories by Tito Sarrionandia on Medium]]></description>
        <link>https://medium.com/@rbs-tito?source=rss-4d05b4515d6------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*XTIYtFcV443lI9onBdbFAQ.jpeg</url>
            <title>Stories by Tito Sarrionandia on Medium</title>
            <link>https://medium.com/@rbs-tito?source=rss-4d05b4515d6------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 00:36:55 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@rbs-tito/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[The senior engineer career hump]]></title>
            <link>https://rbs-tito.medium.com/the-senior-engineer-career-hump-49d84ddc5ebf?source=rss-4d05b4515d6------2</link>
            <guid isPermaLink="false">https://medium.com/p/49d84ddc5ebf</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[careers]]></category>
            <dc:creator><![CDATA[Tito Sarrionandia]]></dc:creator>
            <pubDate>Tue, 28 Dec 2021 16:27:17 GMT</pubDate>
            <atom:updated>2021-12-28T16:27:17.259Z</atom:updated>
            <content:encoded><![CDATA[<p>As a software engineer approaches or reaches the senior engineer role, the things they need to show to progress further become very different. Many engineers don’t explicitly plan for this, and get stuck at what I call the “experience hump”. Here’s how to move past it.</p><p><em>Note: It’s not mandatory to optimise for career growth! It’s very important to some engineers, but do what works for you and your priorities.</em></p><h3>Early career: Experience + competence</h3><p>Early in your career, optimising for experience and competence gets you a very long way. Basically, if you can get someone trusted to say: “They worked on X, Y, and Z and they were pretty good at it”, you’re in a good spot to move forward fast.</p><p>By experience, I don’t necessarily mean years served — there’s not much you can do to optimise for that! Experience also includes the variety and quality of the experiences you have had. Consulting is a great example of a way to gain experiences faster: You might see multiple different industries, multiple different delivery methodologies, multiple different tech stacks all within the space of one year. You might also have been at the right place at the right time, and found yourself leading on a small feature.</p><p>Clearly there’s an upper limit to how much you can accelerate this, it takes time to perfect your craft, but time spent carefully optimising for growth experiences will count for more than time spent in comfortable stagnation.</p><p>Ambitious junior and mid-level engineers are often pretty good at this. They consistently communicate what kind of learning, teams, &amp; situations they want to experience, and make sure they are getting them.</p><p>This works well for a while, but then stops. Usually as you are approaching or just at the senior engineer role.</p><h3>The experience hump</h3><p>You have hit the experience hump, experience alone won’t get you much further. You are now approaching a point where you are able to make or break initiatives. Employers start wanting to hear what you’ve actually <em>achieved</em>. You need to start being able to talk about specific impacts you’ve had, and evaluating what that did to the outcomes that your organisation cares about.</p><p>A more senior colleague vouching that you are performing well in a given situation becomes a “necessary, but not sufficient” condition for your further promotion. Here’s how you start optimising for this new game:</p><h4>Stick around longer</h4><p>When you are in the accumulating experience phase of your career, the market really rewards moving around a lot. It gives you more experience, and it remains unfortunately true that it is often easier to get a better salary by moving employers than by asking for a raise.</p><p>You can probably keep jumping around to get a higher base now too — but you need to start being careful. The impacts of engineering decisions are often felt over multiple years, optimising for your base salary at the expense of getting to own a change over multiple iterations of products and team shape might be a very short term tradeoff.</p><p>Don’t let yourself be taken for a ride and put up with a below market salary, but pick somewhere and see it through. If you’re consulting, you might want to find a permanent role at this point if you aren’t getting the stability needed to do this.</p><h4>Consider specialising</h4><p>Specialising lets you match your impact to specific organisational needs faster, but comes with the risk of having to predict what kind of needs the market will reward.</p><p>Many people choose to specialise around a tech stack, I think there is value in this, but more value in specialising around something more widely relevant to organisations and team shape.</p><p>Security &amp; cloud infrastructure are great examples of this, you move yourself towards more niche roles but you will more rapidly become the expert in the room, which means you more rapidly get to talk about an individual impact that will reassure your current or future employers about your ability to be in a make-or-break position.</p><h4>Get a great mentor</h4><p>Right through your career you should seek mentors who are kind (but honest), supportive, encouraging, and great listeners.</p><p>That’s all still important, but no longer enough. You need at least one mentor who has specific, relevant experience to help you make a bigger impact in your current project. It doesn’t matter how brilliant you are, you’re going to get your impact story faster by surrounding yourself with great advice.</p><p>This means you need to be looking outside of your current organisation, your ability to network here matters a lot. Unfortunately, this is much harder if you’re in an underrepresented group in tech: womens tech networks, black tech networks, LGBT tech networks, disabled tech networks, etc. are likely to be key accelerators for you.</p><p><em>Also, if anyone is reading this who is past this point in their career, this is why it is important to deliberately diversify the group of people you mentor. Don’t leave this to chance.</em></p><h4>Reflect, and write things down</h4><p>You need to find ways to be organised and systematic about reflecting on your successes and failures. Don’t just leave this to your memory. I often find that my brain tends to forget about stressful and broken things after a few months, and that if I don’t document what I was doing and feeling at the time, I will have a rose-tinted view of everything behind me.</p><p>The best place to start here is Pat Kua’s <a href="https://www.patkua.com/blog/an-end-of-year-retrospective-template/">end of year personal retrospective advice</a>.</p><h4>Recognise how flawed we are at evaluating impact</h4><p>I think it’s important to recognise that while this <em>works</em> in terms of landing your next step up, it’s a process incredibly vulnerable to bullshit and egos. Effective leaders with glittering track records have probably made many good decisions, sure, but they’ve also probably been lucky, and benefitted from some privilege along the way. Being at the right place at the right time counts for a lot, and interviewing is not a scentific process.</p><p>I don’t think there’s much you can do with this information, but it feels important to point out!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=49d84ddc5ebf" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Can individuals write code?]]></title>
            <link>https://rbs-tito.medium.com/can-individuals-write-code-29662d7d2d01?source=rss-4d05b4515d6------2</link>
            <guid isPermaLink="false">https://medium.com/p/29662d7d2d01</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[extreme-programming]]></category>
            <category><![CDATA[remote-working]]></category>
            <category><![CDATA[asynchronous]]></category>
            <dc:creator><![CDATA[Tito Sarrionandia]]></dc:creator>
            <pubDate>Sat, 14 Aug 2021 10:54:13 GMT</pubDate>
            <atom:updated>2021-08-16T12:57:50.767Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lQbqLYlcMzmZ7ORj-MnrBg.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@sharonmccutcheon?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Sharon McCutcheon</a> on <a href="https://unsplash.com/s/photos/colours?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Can individuals write code? I think that your answer to this question will, to a large part, predict your attitude towards software engineers being asked to return to the office for all or some of their working week. It describes two nearly-incompatible ways of working, and few people understand that the other way even exists.</p><h3>The dinosaurs</h3><p>Lets look at the clash. Many employers are asking their software developers to return to the office. A vocal and online group of these developers are angry, but most of all confused and perplexed about why their employer would sacrifice the productivity they can achieve by working from a beach villa or scrapping the daily commute.</p><p>The life they permanently want to lead is within grasping distance: Fully asynchronous, totally agnostic of their physical location, fitting around their hobbies and their family. Why would anybody take this away from them if they can sustain their output?</p><p>Big questions generate overly simple answers, here are some I see popping up a lot:</p><ul><li>The companies are dinosaurs, they cannot see that the world has changed, and they are making short sighted decisions because they don’t have the courage to move on.</li><li>The companies want to observe and control you, to monitor your output.</li><li>Immense pressure from commercial real-estate interests forced the decision.</li></ul><p>No doubt there are some old fashioned, cynical employers who think this way. <em>Maybe</em> they are even the majority of mandatory return-to-office employers (though I find that a little hard to swallow.) <strong>I don’t want to talk about those organisations.</strong></p><p>Occasionally, I see a Tweet or a comment on LinkedIn from somebody who is not a corporate director saying something like: “Co-located teams are always more productive than remote teams”, or “Remote teams are worse at innovating”. This person will be shot down immediately.</p><p>If you view this as a clash between cynical dinosaurs vs creative brilliance, then the developer taking the side of the dinosaurs must be a sell-out, or brainwashed.</p><p>Here’s another way to see the clash: Individual vs Group oriented production.</p><h3>Individual oriented production</h3><p>This is by far the most common way to organise people to produce software, and is the way I used to work back in 2011.</p><p>At the time, I was building ecommerce software using <a href="https://www.sap.com/uk/acquired-brands/what-is-hybris.html">Hybris</a> and Java. I was working in an office (with a nice view of Buckingham Palace), I had a desk and an iMac that were permanently assigned to me.</p><p>The work I was doing was often challenging, with complex refactors that made me sketch class diagrams to get right, but it was extremely well understood.</p><p>At the time, most brands we worked with just wanted a web shop. Occasionally they’d have a loyalty card system or something to integrate with, but more often than not it was search, carts, accounts, order management — and it all worked the same way.</p><p>I worked solo 95% of the day. Unless I was really stuck and couldn’t unblock myself, more often than not I’d work with my headphones on. I’d find it incredibly annoying if somebody interrupted me, breaking my flow. I hated meetings.</p><p>I think this is the most common way of experiencing offices as a developer. Your work is individual, focussed, and deep — and the office (especially the dreaded <em>open plan office</em>) is trying to fight against you, and distract you from doing your actual work. I believe that for many people engaging in the debate, this is the <em>only</em> way they have worked.</p><p>I’ll call this individual oriented production. There are lots of flavours of it, of course: Open source projects, fully remote asynchronous organisations, developers in cubicles in a shared office space, etc.</p><p>These are teams where people mostly work solo, where their time spent writing code is considered precious enough to protect it by defining requirements clearly in advance, where individual ownership of pieces of the solution is rewarded, and where uninterrupted flow is the ultimate sign of efficiency.</p><p>The defining characteristic of these teams is that the team’s productivity is equal to the sum of the outputs of each developer.</p><h3>Group oriented production</h3><p>By 2015, I had totally changed my outlook. The way I liked to work had become intensely conversational. I was in favour of two engineers working with one single keyboard, of doing requirements analysis at the same time as we were writing code to meet those requirements, programming was more about using my voice than my keyboard. I liked there to be other pairs of engineers working in ear shot so we could eavesdrop on each other and come in with helpful extra pieces of information.</p><p>I was pretty much doing a different job. While there are of course crossover skills between these two jobs, they feel as different to me now as driving a car and flying an aeroplane.</p><p>I’ll call this group oriented production. Again, there are many flavours: Extreme Programming, Mobbing, etc.</p><p>These are teams where people mostly work in groups, where there is intense resistance to attributing any success or failure to an individual, where developers only ever seem to spend 5–10 minutes actually writing any code before diving right back into a conversation again, and where the interface to developers is to tell them about a problem, not a requirement.</p><p>The defining characteristic of these teams is that the team’s productivity is equal to the successful facilitation of contrasting skillsets and interpersonal dynamics.</p><p>In short, they are teams where <strong>individuals cannot write code,</strong> groups write code.</p><h3>Contrasting behaviours</h3><p>These two archetypes require extremely different behaviours and skillsets to operate in. You need to know how to write code in both, but beyond that they are almost different jobs. It’s like seeing surgeons and playwrights arguing about whether or not working from home is viable.</p><h4>Brain space</h4><p>In individual oriented production, the most productive people often have an incredible capacity for in-brain working memory. The times I felt most productive was where I could have a huge system sketched out in my head, balancing on the edge of forgetting a little detail, figuring out where my change sits and what it might affect. This is a really fun skill to develop, and is directly connected to the idea of flow. If you’re visualising a big structure in your head, and then somebody comes to your desk and asks about your expense report, they destroy a huge amount of the time you have spent.</p><p>In group oriented production, you need to be good at choosing tiny steps and guiding the emergent design of a system, one little choice at a time. Are you going to build a system that does some complex financial settlement? You might start by defining a unit test for what happens if someone tries to input <strong>null</strong> instead of a transaction. Write a test, get it working, commit the change, move on. Your working pattern is a mini conversation, 5–10 minutes of coding and simultaneous discussion, rinse and repeat. You need to be masterful at predicting how these tiny changes will add up to the overall system that will eventually exist. Your brain space can be small (great news for me!), so long as you have some strategic patterns in mind to predict the likely emergent effect you are having on an architecture.</p><h4>Requirements</h4><p>In individual oriented production, you kind of need to know where you’re going before you start. Your working pattern should include flow, so you want to get all of those interruptions and distractions out of the way early. You need to be good at reading into the detail of requirements, and anticipating all of your clarifying questions in advance. If you do this well enough, you can get multiple hours of flow in a day.</p><p>In group oriented production, you aren’t optimising for flow at all, so getting everything clear right at the start matters way less. Instead, you need to be good at prioritising your questions: What are the fundamental questions that we need to even pick a direction? What are the questions that we can just figure out as we go? What are the questions that don’t seem to matter much, and we can just risk getting wrong? You also need to be good at bringing in the right people at the right time: Roughly when do we think an expert designer or product manager would be good to collaborate with?</p><h4>Consensus</h4><p>In individual oriented production, you get to make a lot of calls. While there will probably be a process of code review, your career progression will be partially down to how good you are at calling the shots when it comes to building the components you are assigned. The important thing here is to get good at making a call and documenting the call you made. One thing I sometimes observe here is that if you build a feature, commit to owning it, and continue to iterate on it as an individual — you have done a fantastic job. You solved the teams problem by yourself, freeing them up to solve other problems.</p><p>In group oriented production, it’s more about evolving your team consensus. A consensus might be something like “In general, we apply this pattern in this situation”. This might also include documentation, of course, but you might find that it’s more effective to use demonstrations or mobbing to spread consensus instead or in addition. Here I observe the complete opposite response to the same situation. If you build a fantastic feature, but there are not others in the team who came along the journey with you, who fully grasp each part of the tradeoffs made, the strengths and limitations of its design: You have completely failed to do your job, because you introduced an individual dependency, and harmed the teams ability to operate as a collective.</p><h3>Isn’t this about asynchronous rather than remote?</h3><p>Yes! As <a href="https://twitter.com/allenholub">Allen Holub</a> has pointed out a number of times, there is an annoying conflation between remote ways of working and asynchronous ways of working. In reality, remote synchronous teams (that is, where everybody collaborates using online tools in real time) <strong>are</strong> group oriented production teams.</p><p>These two issues have become deeply linked however, for two reasons:</p><ol><li>The loudest advocates of permanently leaving the office behind are also advocates of asynchronous development, to the extent that you cannot talk about a remote first plan without tackling the synchronicity problem head first. I see comments such as “If you’ve gone remote and you’re trying to recreate your old ways of working online, you’re doing it wrong”. I’ve seen remote working presented as a step on an evolutionary scale to fully asynchronous ways of working. This is almost received wisdom at this point, so if you want to answer the remote question you <strong>must</strong> simultaneously answer the asynchronous question for it to make sense to anyone.</li><li>I think they are actually fundamentally connected if you see them as <strong>enablers of group oriented production, </strong>it’s just that one massively overshadows the other. If synchronicity gives you 80 points on the Group Oriented Production meter, physical co-location gives you an extra 10 points.</li></ol><h3>Is this an arbitrary choice?</h3><p>Almost certainly not. Each solution has its advocates, and I suspect that as we see a strong bifurcation in the market (as the question is forced by the working from home debate) we will see people starting to understand more about which contexts highly collaborative or asynchronous problem solving is more appropriate.</p><p>I’m reminded of how Simon Wardley describes the people who break organisations by insisting on “Agile everywhere!”, whereas his maps show that there are some highly commodified, highly understood sections of the business where Six Sigma might well make more sense.</p><p>For individual oriented production, I suspect the office question is a done deal. There are very few advantages that anyone can point to of working solo in one place vs working solo in another. Companies that want to do individual oriented production but also insist on returning to work are probably going to be left behind.</p><p>For group oriented production, there are going to be a wider range of views. If collaboration in real time is the advantage, then clearly there will be some people who prefer facial expressions and whiteboards to zoom and miro, but equally there will be people for whom that difference is not stark enough to sacrifice the ability to spend some extra time at home. All points on the scale of fully remote to fully co-located feel like reasonable decisions for a team to make when they are working as a collective.</p><p>As I hinted at when describing my old ecommerce job, I suspect that how well understood a problem is might be a contributer here. My switch from favouring individual to group oriented production coincided with my switch from building things that my team and my customer fully understood, to getting building things by getting around a whiteboard and saying “What are we even trying to achieve here?”</p><p>There may well be other facets that we learn to consider, and we must learn to trade off productivity with other factors (access to talent pools, employment benefits, problems that require input from people in different time zones, etc.)</p><p>Above all though, we need to learn to ignore people selling real estate or remote working software and make our own decisions.</p><h3>Feedback</h3><p>I sometimes go back and edit these articles, so do feel free to <a href="https://twitter.com/rbs_tito">tweet me some feedback</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=29662d7d2d01" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Improve Your Security By Talking About Gardening]]></title>
            <link>https://medium.com/swlh/improve-your-security-by-talking-about-gardening-c48ea15ae9eb?source=rss-4d05b4515d6------2</link>
            <guid isPermaLink="false">https://medium.com/p/c48ea15ae9eb</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Tito Sarrionandia]]></dc:creator>
            <pubDate>Thu, 25 Feb 2021 11:59:16 GMT</pubDate>
            <atom:updated>2021-03-21T08:34:34.643Z</atom:updated>
            <content:encoded><![CDATA[<p>I am convinced that banging on and on about warfare is hurting our ability to make pragmatic, cultural changes that protect our software and our organisations.</p><p>It’s dangerous to just accept metaphors as a way of describing the world. In many cases, that act of description changes the way you see the world — it is <strong>performative. </strong>I’m not even talking about using inclusive language, although that’s important too, I’m just talking about whether or not a particular metaphor encourages people to think about the right things at the right time.</p><p>Early on in my tech career, much of the things I learned about security were described to me in terms of warfare. I attended developer talks with Sun Tzu quotes, learned what a <a href="https://en.wikipedia.org/wiki/DMZ_(computing)">DMZ </a>is for, and heard the value of threat modelling is described as “knowing your enemy”.</p><p>I think gardening is a better metaphor. Not only is it more accessible (let’s face it, the IT consultant with a camo laptop case knows next to nothing about how to conduct warfare), but it emphasises a few things that I think are missing from the military analogy.</p><p>Obviously this isn’t true for every context, maybe in your context warfare (or something totally different) works better — but I think it works better for many of the organisations I’ve found myself in, including government teams working on regular citizen-facing services.</p><p>The rest of this post is a hodge podge list of ways in which it is a more useful metaphor than warfare, accompanied by some photographs I like.</p><h3>It emphasises the nice things you want to build.</h3><figure><img alt="A path through a rose garden" src="https://cdn-images-1.medium.com/max/1024/1*RoM97DdyqkXnerK6-TNpJw.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@mioitophotography?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">MIO ITO</a> on <a href="https://unsplash.com/s/photos/garden?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>When you are gardening, you might need to go “on the offensive” now and then. For example, weeding, or putting down slug repellant.</p><p>But it’s really clear <strong>why</strong> you want to do that. You put down slug repellant because you want nice cabbages, you pull up the weeds before they grow tall to give the geraniums a chance to grow.</p><p>At no point does it become an all out existential conflict against slugs or dandelions. States become involved in long, moral, tit for tat conflicts against each other that sometimes lead to war.</p><p>The notion of a “total war” on slugs would be absurd in a gardening setting. Would you salt the flowerbeds and concrete over the lawn to stop the slugs? Obviously not. Because stopping the slugs doesn’t ever become a top level moral priority, protecting the veg patch is.</p><p>In the same way, your security should be obsessively focussing on the nice things you want to build and maintain. You lock down access <strong>so that </strong>people feel safe giving you their data, you rate limit the API <strong>so that</strong> your human users can have a smoother experience.</p><h3>The enemy is unknown.</h3><figure><img alt="A caterpillar on a leaf" src="https://cdn-images-1.medium.com/max/1024/1*KyoE5faXezfXv5HGHtSU9A.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@fields_th?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Thomas Fields</a> on <a href="https://unsplash.com/s/photos/caterpillar?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Gardeners might not even know who the enemy is. You see something has been nibbling at the leaves — is it a caterpillar? Is it a slug? You can ask other gardeners or read books to see if the pattern looks familiar to them. Sometimes it will be, sometimes it won’t.</p><p>There is no geneva convention requiring the aphids to wear a uniform, and you can’t even track down who manufactured and sold the weapons.</p><p>This is even a problem in actual cyber warfare. Sean Lawson <a href="https://firstmonday.org/ojs/index.php/fm/article/view/3848/3270">criticises the use of military analogies </a>in state-on-state cyber attacks, at one point drawing attention to what he calls “a crisis of cause and effect”.</p><p>The attacker is anonymous. You can’t credibly threaten them, you will struggle to reason too much about their individual motives. You can reason in broad terms to try and figure out how much trouble they will go to to get at your database, but that’s about it. In the same way, you might reason that slugs love eating basil, so you might need some extra slug proof defences around the basil, but it would be pointless to try and second guess the strategies and behaviour of individual slugs.</p><h3>The enemy is impersonal.</h3><figure><img alt="Three ants on a leaf" src="https://cdn-images-1.medium.com/max/1024/1*WLR82UXyVKMhwCGRpBIMVg.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@salijareer?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">MD_JERRY</a> on <a href="https://unsplash.com/s/photos/ants?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>This isn’t always true — but many of the things you are defending against really have nothing to do with <strong>you </strong>at all. Nobody cares that it is <strong>your</strong> database, they just care that you left it exposed with a default password.</p><p>Many of the threats you want to reason about are purely transactional, or maybe even random. The <a href="https://en.wikipedia.org/wiki/Script_kiddie">script kiddie </a>as an archetype is well known. They really don’t care whether they’re targeting a bank, a government, or the webpage for the local running club: They just care that it’s deployed on a version of wordpress that they know an exploit for. They might have scanned the web at random to find your website, and you just got unlucky to be an early hit.</p><p>If a gardener started by trying to think about which animals might be personally motivated to ruin their flowerbed, that would be pointless. The insects don’t know or care that it is <strong>your</strong> flowerbed, they just care that its made of flowers and they were able to easily crawl to it.</p><h3>The enemy is you.</h3><figure><img alt="Two people stamping in puddles." src="https://cdn-images-1.medium.com/max/1024/1*NaKRtYeyawQwUEvjO_ppMA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@joshcala?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Josh Calabrese</a> on <a href="https://unsplash.com/s/photos/muddy?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Gardeners break their own gardens all the time. Over-watering, under-watering, accidentally stepping on a plant, using a pot that’s too small, getting the leaves wet before a scorching hot day, etc.</p><p>Software teams do this too. We migrate the wrong database, lose access to an important account, introduce a defect, forget to test a feature with a screen reader, etc.</p><p>It is absolutely not the case that everyone <strong>within the garden </strong>(or team) can be trusted<strong>.</strong> As a matter of historical truth, I have done far more damage to my users and their goals than any cyber attacker has!</p><p>Gardeners and software teams need to learn to live with that (the garden won’t always look pristine, and that’s ok), introduce antifragility to recover from it (plant multiple types of thing in the veg patch), introduce checks and balances to remind themselves to do the right thing (check the weather and write up a watering schedule).</p><h3>Sometimes, the enemy isn’t an enemy at all.</h3><figure><img alt="A fox sitting amongst some flowers and tall grass." src="https://cdn-images-1.medium.com/max/1024/1*Hd5weofFRbXGwrZMdULiXg.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@nathananderson?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Nathan Anderson</a> on <a href="https://unsplash.com/s/photos/fox?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>I’ve already pointed out that animals aren’t out to get you, but it’s more than that — their entire status as a threat or a welcome presence depends on how you build your garden.</p><p>Bees are good for your garden, but it will be incredibly annoying if they are always flying through the kitchen window. You can solve this by planting lots of bee friendly flowers a little distance away from the kitchen window.</p><p>Foxes might trample the flowers, but if you make the flowers a little bit harder to get to, and make other parts of the garden more attractive for them to spend time in at night, then they might become completely benign visitors.</p><p>The problem isn’t the presence of the animals at all, it’s just the environment they’re in. In the same way, your actual users might cause a nuisance if you build things wrong.</p><p>Have you got a long running transaction that makes your users refresh the page a bunch of times in frustration and increase server load? It’s not their fault, it’s just about how you designed the website.</p><h3>Experimentation is a good idea.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*E3EvtQJHs7VCg5PjhMsuHw.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@struvictoryart?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Victoria Strukovskaya</a> on <a href="https://unsplash.com/s/photos/different-flowers?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Experimentation obviously exists in a military setting, but that’s fairly dark and it would be hard to describe it as unambigously a good thing. The consequences of decisions in warfare are, more often than not, tragic.</p><p>In a gardening setting, and in the majority of application security settings, you’ve got to try things out to know if they work. I’ve been in sitatuations where we’ve seen a particular type of attack, so we study it and try out a new way to identify it, wait for it to happen again then add another layer, and so on.</p><p>We would never have got it right if we just guessed at what we needed up front. Our context was a little bit unique, so different things had different effects to any previous context we had been in.</p><p>Gardeners also do this. You start out with a basic approach that lots of people seem to recommend, then see what happens. If it doesn’t work, you start to think about some of the other variables. Maybe your soil has a particularly high clay content; maybe the elevation leaves the plant exposed to the wind.</p><p>You keep researching, you ask questions of other enthusiasts, and you try something new. You might even plant multiple plants in slightly different conditions to see what works best.</p><h3>Little and often usually makes things work better.</h3><figure><img alt="Some gardening tools in a greenhouse." src="https://cdn-images-1.medium.com/max/1024/1*PhxuG1KFqqPL8MBaC3GVLw.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@anniespratt?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Annie Spratt</a> on <a href="https://unsplash.com/s/photos/trowel?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p><a href="https://martinfowler.com/articles/agile-threat-modelling.html">This article by Jim Gumbley </a>was transformative for my ability to make pragmatic change to the behaviour of teams around cyber security. Jim makes a compelling case for starting simple and expanding your threat model over time.</p><p>I’ve seen so many teams get lost trying to reason about all threats across their whole product, but when we starting talking about the threats <strong>to a particular flow</strong>, they generated a huge amount of useful data that allowed us to proactively invest in security much earlier than we otherwise could.</p><p>This is also what gardeners do. A bit of weeding one day, a bit of pruning the next, tidying up the tool shed now and then. Gardens are living, organic, complex systems (just like teams), and as such your investment in them needs to be continuous.</p><p>Additionally, monumental changes can actually be a bad thing. If you rip out all of the plants and soil from your garden to start again with something new, you will lose some of the nutrients built up over centuries, you’ll lose the organic serendipity that formed (the tree grew in that patch 40 years ago <strong>because</strong> the light suited it so well). If you rip up your software and your processes overnight and replace it with a cookie-cutter solution, you end up with a complexity that people don’t understand, and a set of processes that were not formed according to the needs and preferences of the actual humans that are expected to carry them out.</p><h3>Final caveats</h3><ol><li>Your context may very. Obviously. Pick a metaphor that works for you and what you are doing.</li><li>I’m not actually a gardener! I do, however, love reading and listening to gardening content. Gardeners employ a mixture of old wisdom, new ideas, experimentation and enthusiasm to build nice things in a way I find to be completely infectious.</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c48ea15ae9eb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/improve-your-security-by-talking-about-gardening-c48ea15ae9eb">Improve Your Security By Talking About Gardening</a> was originally published in <a href="https://medium.com/swlh">The Startup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Continuous integration: Pipelines or jobs first?]]></title>
            <link>https://rbs-tito.medium.com/continuous-integration-pipelines-or-jobs-first-86d0fa440e17?source=rss-4d05b4515d6------2</link>
            <guid isPermaLink="false">https://medium.com/p/86d0fa440e17</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[continuous-delivery]]></category>
            <category><![CDATA[continuous-integration]]></category>
            <dc:creator><![CDATA[Tito Sarrionandia]]></dc:creator>
            <pubDate>Thu, 04 Feb 2021 22:14:28 GMT</pubDate>
            <atom:updated>2021-02-04T22:22:26.244Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SIdFX9WKnhybbaemGzcgkg.jpeg" /></figure><p>Recently I found myself wanting to express an opinion about continuous integration pipelines to my team, but I lacked the language to do it. I’ve been searching the web for days now, and <a href="https://twitter.com/rbs_tito/status/1356522103319777280">asking on Twitter</a>, and I still can’t find any good description of what I’m talking about. So I’m going to try to describe it here.</p><p>I’m kind of hoping that somebody sees this and then points out that I wasted my time because it’s already well described elsewhere, so I’ll finally have a resource to point at!</p><p>The thing I want to describe is a design difference between continuous integration systems. I’m going to call it pipeline-first vs job-first continuous integration.</p><p><strong>Job-first </strong>continuous integration systems seem to be most common right now. Confusingly, they all claim to be pipeline based, but I think they mean something subtly different to the idea of “pipeline-first” that I’m trying to get across.</p><p>To a job first system, the whole world can be seen as a number of jobs, or tasks, or build stages, that you perform <strong>on a given change. </strong>Good examples are CircleCI, GitHub actions, and (I think) Azure Pipelines.</p><p>Job-first systems are probably more simple to get your head around. Every time a change is made, the codebase as it existed after that change is run through some jobs. Often, these jobs are in that exact same codebase, which makes everything lovely and repeatable for any given change.</p><p>There can be multiple jobs for each change, and those jobs can be run sequentially, in parallel, or some mixture of the two. If you string a few jobs together, you’ve got a pipeline.</p><p>Every subsequent change generates its own set of jobs, and these run completely independently from the last change.</p><p>This is different to a pipeline-first system. Pipeline-first systems appear similar: They also allow you to define a number of jobs in sequence and in parallel, they let you string these together into a pipeline, and they let you define these in the same codebase as the thing being built.</p><p>The crucial difference though, is that the pipeline is the first order object. That is, you have a single pipeline and all of your changes move down it sequentially — instead of every change having its own pipeline that runs in a sandbox. Examples of this pattern are Go-CD, AWS CodePipeline, and ConcourseCI.</p><p>The difference in behaviour is small, but I think it’s actually fairly important if you’re trying to optimise for flow. Either design might fit your situation better depending on what you are doing.</p><h3>Worked example</h3><p>I’m going to work through an example. In the example I’ll assume all changes are being committed straight to Trunk, but I think all systems support building on branches too. I’m doing this firstly because it’s way easier to draw, and secondly because it’s <a href="https://trunkbaseddevelopment.com/">the way I like to build software</a>.</p><figure><img alt="A pipeline with these stages: Download src, build and test, release to staging environment, manual approval, release to prod" src="https://cdn-images-1.medium.com/max/171/1*1zFtje2iq3FD009hislQvA.png" /></figure><p>Imagine your build process looks like this. It’s a simple linear process made up of 5 steps.</p><ol><li>Download src: This is triggered automatically when you push a change to Git.</li><li>Next, the downloaded source code goes through build &amp; test. The code is compiled, and some tests are run against it.</li><li>The code is then automatically released to a staging environment</li><li>This stage is manual. A developer has to click a button to allow a change to go through.</li><li>The final stage releases the code to production.</li></ol><p>Now imagine that several commits are made to trunk in quick succession. Commit 1 is a refactor, commit 2 is a new feature, and commit 3 is a fix for a performance issue you are experiencing. Commit 2 unfortunately introduces a defect, which stops the tests from passing, so this problem is fixed in commit 4.</p><h4>Job-First</h4><p>On a job-first system, all three commits are running through their own pipeline separately, and you’ll end up with an output looking something like this. Green means complete, yellow means in progress, red means failed.</p><figure><img alt="Four versions of the pipeline. Commits 1 and 4 have got to manual approval, commits 2 and 3 failed on build and test." src="https://cdn-images-1.medium.com/max/801/1*Z5-GXgQg5SWUUos7QReEbg.png" /></figure><p>Commit 1 makes it all the way to manual approval. Commit 2 fails at build and test, so stops there. Commit 3 also contains the defect introduced in commit 2, so also stops there. Commit 4 fixes the defect, so makes it all the way through to manual approval.</p><p>At this point, you could choose to approve commit 1 or commit 4 to be production. You could also choose to release commit 1, then commit 4 to production.</p><h4>Pipeline-First</h4><p>It’s harder to draw what would happen in a pipeline-first situation, you need to think about how it would look at different times.</p><p>Here is the pipeline after commit 1 has got all the way to manual approval.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/941/1*74Ht3kmSDkxcWs67COYLVg.png" /><figcaption>Note that there is now only 1 pipeline, and each stage tells you what it is currently building, or the last thing it did build.</figcaption></figure><p>Next, imagine you click manual approval, and just as your code makes it into production, commits 2 and 3 are merged to Trunk.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/941/1*V_UR3VUQX0ge2K11tkmugg.png" /><figcaption>There is only one pipeline, and each job is dealing with a different commit.</figcaption></figure><p>Build and test is currently building commit 2. Download src has finished downloading commit 3. This is the next key difference: <strong>Commit 3 cannot go through build &amp; test until commit 2 has finished.</strong> They are queued up, just like a factory conveyor belt.</p><p>Of course, we know commit 2 will fail to get through build and test. Lets imagine it did fail, at this point commit 3 will move in to build and test. Lets introduce a new colour: Orange means “currently building, but last build was a failure”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/941/1*wIAZ42l_g3nZ_RYdGQxrzQ.png" /></figure><p>Commit 2 is, at this point, history. On most systems you can click into a job and get it to run an older build if you want. This is sometimes useful if you think that you’re dealing with a flaky test. Commit 2 also cannot be released to staging or production, even if you want to. It won’t ever get there because you can’t skip stages in the pipeline. The factory analogy mostly holds here too: You can’t put the windows on the car unless you’ve put the doors in first.</p><p>Next, commit 3 will fail too, but commit 4 has just been downloaded.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/941/1*LYI3FYgjifeEvLCm76gTkQ.png" /></figure><p>Next, commit 4 moves into Build &amp; Test…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/941/1*oZ7Zz6Y7w9qylSgtlt7Vlg.png" /></figure><p>Then finally, it passes and moves into manual approval.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/941/1*ZMuJka6hHFITAb1Yeu-vCQ.png" /></figure><h3>Does it matter?</h3><p>I think it does. I’m struggling to articulate exactly why, but this is my best shot at why I prefer the pipeline-first system:</p><ul><li>Guaranteeing that one commit cannot pass through a stage before the previous one psychologically prepares me to <strong>think about just one change </strong>at a time. If I’m the author of commit 3, and a different person wrote commit 2, in the jobs first system I’m mostly watching my own commit. In the pipeline-first system I’m watching <strong>everyone’s</strong> commits move through the same pipeline and so I’m hyper-aware of the context of my incremental change. Of course I technically can get the same data from the job-first system by looking back at commit 2 and seeing that it introduced the defect, but I’m not constantly tracking how all the changes my team are making are doing.</li><li>I think it also psychologically sets me up better to practice <a href="https://en.wikipedia.org/wiki/Andon_(manufacturing)">Andon</a> (everyone stops work when the build breaks and focusses on fixing it). If I’m looking at one single pipeline and watching peoples changes go through it, I might not even have made commit 3. I might have seen that the build went red for commit 3, and so joined the authors on fixing it so that I know that my commit is a change off of a reliably clean base. Easier to think about. Again, I technically <strong>could</strong> do this with a job-first system by having some sort of alerting on all commits, but the shared team view of a pipeline adds significant social pressure on me to behave this way.</li><li>If I’m aiming for continuous delivery, and looking to remove that manual phase from the pipeline so that every passing commit sails straight into production without human intervention, guaranteeing that the build phases only run in the intended order is actually pretty important. If a phase of my pipeline has a slightly unpredictable time (this often happens in UI tests that use timeouts and retries), I might end up with two commits racing to production. If the newest commit makes it first, then the older commit will be released on top of it.<br>Of course, most job-first systems will let you do something clever to prevent this, but I find it takes up less brain space to just have a hard and fast queuing rule. When it comes to production changes, I want to make it as simple as possible to understand so that my dumb monkey brain has half a chance of not screwing it up.</li></ul><p>That said, there are definite disadvantages to pipelines-first, notably:</p><ul><li>If your commit traffic is high and your jobs take a while, a queue can really slow down your development feedback loop.</li><li>There’s some weirdness where in general the pipeline comes first, but the pipeline itself is defined in source so the structure of the whole pipeline is defined by the newest commit. So if you change something, it’s immediately applied across the pipeline, possibly including the definitions of the jobs that the older commits are still passing through! 🤯</li></ul><p>This feels incredibly subjective — I’d love to know how other people have applied incremental change mindsets in either system. I’d also love to know if these patterns have real names and are actually documented somewhere!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=86d0fa440e17" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why I’ve stopped holding people accountable]]></title>
            <link>https://rbs-tito.medium.com/why-ive-stopped-holding-people-accountable-70a020909b9e?source=rss-4d05b4515d6------2</link>
            <guid isPermaLink="false">https://medium.com/p/70a020909b9e</guid>
            <category><![CDATA[management-and-leadership]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Tito Sarrionandia]]></dc:creator>
            <pubDate>Sun, 31 Jan 2021 20:44:38 GMT</pubDate>
            <atom:updated>2022-10-24T14:07:49.942Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Some Star Wars figurines" src="https://cdn-images-1.medium.com/max/1024/1*pNYT4y26LR-hnKgkUNrIEg.jpeg" /></figure><p><strong>EDIT:</strong> There are parts of this that I don’t really agree with anymore, I’ve probably mellowed a little overall, but I did turn it into a conference talk that I mostly still stand by.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FnmR9wVs_2zg%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DnmR9wVs_2zg&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FnmR9wVs_2zg%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/e515af596eb532b81b3a20f5f55d87af/href">https://medium.com/media/e515af596eb532b81b3a20f5f55d87af/href</a></iframe><p>I’m extremely sceptical about the commonplace notions of “accountability” and “responsibility”. I think there is a fundamental tension between these concepts and a desire to create psychological safety on a team. In this post I’ll talk a little bit about why they are hard to balance, and what I’m now doing instead.</p><h3>What is accountability?</h3><p>This is surprisingly tricky to answer. At some level, it means that you <strong>own</strong> <strong>the consequences </strong>of some decisions.</p><p>It is sometimes understood in contrast to responsibility. An engineer might be <strong>responsible</strong> for fixing a defect, because they are the ones that actually write the code; whereas a team lead might be <strong>accountable</strong> for fixing defects, because they are the one that gets to make the decisions about what the team is working on, even if they don’t directly fix the defects themselves.</p><p>Sometimes, you will see this expressed as a <strong>RACI matrix</strong>. This is a grid explaining who are the Responsible, Accountable, Consulted, and Informed individuals for any given process, deliverable, or outcome.</p><p>Received wisdom about accountability is that you must <strong>only ever have a single accountable person</strong> for any given outcome. In the words of <a href="https://www.cio.com/article/2395825/project-management-how-to-design-a-successful-raci-project-plan.html">this guide,</a> “<em>the buck stops there</em>”.</p><p><a href="https://www.linkedin.com/pulse/raci-responsibility-model-explained-star-wars-matthew-inman/">The best explanation I’ve found uses Star Wars </a>as an analogy. While Darth Vader is <em>accountable</em> for destroying the Jedi, it is often delegated to bounty hunters, who are <em>responsible.</em></p><h3>Smells</h3><p><a href="https://martinfowler.com/bliki/CodeSmell.html">Code smells </a>are a useful way to describe code quality. They refer to things you might observe that aren’t <strong>always</strong> a problem — but, like a bad smell, are often the sign of something bad, and so should at least be investigated.</p><p>On this metric, the RACI idea stinks. Here are some management smells:</p><ul><li>The single accountable person “rule” is often treated like it needs no further justification. I cannot find a justification for it that matches any context I’ve worked in: most justifications seem to come from Taylorist organisation design or the military.</li><li>It doesn’t actually sound anything like the best teams I’ve worked on. When I think about the most productive, most outcomes focussed teams I’ve worked on, they didn’t behave like this at all. Nobody counted each others contributions. Leadership was fluid, all praise was accepted as a collective, all mistakes were dealt with as a collective. In short, we lived and breathed the <a href="https://retrospectivewiki.org/index.php?title=The_Prime_Directive">Prime Directive </a>all week long.</li><li>It requires mental gymnastics to make it sound blameless. “The buck stops here” <em>really means </em>“I’m happy for you to keep playing at this agile thing, but I need to know who to fire if I don’t get exactly what I want”. It can only ever be a threat. If you don’t believe me, buy a coffee for your friend and then tell them you’ll be <strong>holding them accountable </strong>for buying the coffee next time.</li><li>The fact that the most convincing explanation of RACI I can find has its roots in the management structure of an intergalactic genocidal military empire ruled by a religious cult raises some alarm bells.</li></ul><h3>Collective accountability</h3><p>I’ve already hinted at what I think good looks like: a team of experimenters who have the knowledge and the power to constantly challenge their entire end to end process.</p><p>The process is everything and belongs to everyone, so they take both praise and criticism as a collective. Individuals do get feedback, but it is not framed as an evaluation of their performance, it is a useful stream of data thay they are trusted to deploy as they see fit.</p><p>When things go wrong, nobody piles “fault” on the person who happened to press the button, instead they reflect on the process and how it allowed a single point of failure to materialise.</p><p>Mistakes are celebrated as learning opportunities. This is so baked in to every cultural signal, that the individual who did happen to press the button will have no qualms about standing up in front of the rest of the company and proudly showing off what was learned. The idea that this might be met with some sort of punishment is simple inconceivable to them.</p><p>This is my favourite way to build psychological safety. Psychological safety is a necessary pre-requisite for experimentation, because human beings cannot be expected to be honest if doing so will materially harm then.</p><p>Moreover, it is inhumane to ask people to work without psychological safety. The emotional labour of trying to do your best while also covering your back is not a sustainable burden.</p><p><em>Note: </em>This does <strong>not</strong> mean that you can run a team without individual performance management. Performance management can also conflict with psychological safety, and is hard to get right. Paradoxically, however, it is also necessary for collective responsibility — because individuals on the team can’t lean into the process unless the team can guarantee some base level of stability.</p><h3>Value statements</h3><p>Of course, you will still have some special roles on the team, and this is where I most often see RACI deployed in agile organisations. Product managers, delivery managers, and tech leads are fairly common special roles.</p><p>For these, I’ve started using simple value statements. These are single sentence descriptors of how people in special roles should be evaluating their actions and priorities.</p><p>Here’s one we gave to an engineering lead recently:</p><blockquote><em>Value added: The team knows what it means to build something the right way, and is empowered to continuously improve its engineering practices.</em></blockquote><p>These statements must be short, they must not say <strong>what</strong> an individual is expected to do, and they must describe all value through intended impact on the team.</p><p>They must be owned by the team as a whole, and the individuals in the particular roles must be open to the team deciding in a retrospective that the special role needs adjusting or removing. They must have the psychological safety to know their skills will be valued regardless of if their role on one particular team changes.</p><p>Here’s why I prefer it this way:</p><ul><li>They are both faster and more fun to write.</li><li>They focus on the positive. They are aspirational and ambitious statements, not thinly veiled threats outlining bare minimum performance.</li><li>They do not conflate individual performance management with a particular project or outcome. While these things are connected, they do not need to be managed at precisely the same time.</li><li>They do not focus on specific tasks, meaning there is less incentive to cling on to a special role, rathern than working to make it redundant through wider team participation or automation.</li><li>They are friendly to the growth of more junior team members, allowing other team members to try specific tasks they have not tried before, and thereby increasing resilience.</li><li>They don’t take particular <strong>outputs</strong> as a starting point. They allow for the possibility that everything being done requires improvement or replacement.</li><li>They are accessible to people who don’t ever intend to listen to a management seminar.</li></ul><p>They don’t completely solve that tension between accountability and psychological safety. At their worst, they might be used as a veneer to cover up threatening behaviour. It’s probably true that all organisations under capitalism are, at some level, threat driven.</p><p>Still, I’ve seen them encourage collaboration and disincentivise territorialism — and I think that makes teams just a little bit nicer to work in.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=70a020909b9e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The resilience of mixed seniority engineering teams]]></title>
            <link>https://rbs-tito.medium.com/the-resilience-of-mixed-seniority-engineering-teams-eacb98f185d1?source=rss-4d05b4515d6------2</link>
            <guid isPermaLink="false">https://medium.com/p/eacb98f185d1</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[engineering-mangement]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Tito Sarrionandia]]></dc:creator>
            <pubDate>Wed, 13 Jan 2021 22:45:09 GMT</pubDate>
            <atom:updated>2021-01-13T22:53:00.085Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xhoOuzWDGpK9Ii8oFT8c3w.jpeg" /></figure><p>A couple of weeks ago I wrote this line in some <a href="https://rbs-tito.medium.com/lessons-learned-from-building-a-government-service-883dcc8d8f24">lessons learned from building a new digital service </a>for the UK Government:</p><blockquote><em>I’m extremely proud of how we managed to do that with an unremarkable budget and a team with multiple junior members.</em></blockquote><p>It seemed to resonate. A few people reached out to me on Twitter asking me about their own organisation and whether they too could incorporate more junior roles into their engineering teams.</p><p>It’s true that you need to do a fair bit of work to responsibly support people earlier in their career — but this isn’t a question of learning what you have to do to build performant teams <em>despite </em>the presence of junior members, it’s about recognising that you can build performant teams <strong>precisely because</strong> <strong>you have a mixed seniority team</strong>.</p><p>There are two big reasons why:</p><h3>1. Your internal communications will bloom</h3><p><a href="https://twitter.com/drjharrison">Dr. J </a>is a consultant at ThoughtWorks, and a good friend of mine. When we worked together, they were always pointing out how being inclusive to one person often makes things better for whole teams. For example: you might start captioning your all-hands events to better include a deaf team member, and then learn that your team members who don’t speak English as a first language are also loving the captions because it helps with unfamiliar accents.</p><p>If you mix up your teams seniority levels, you will see this exact multiplier effect over and over again in your internal communications. As an engineering director, this is literally the closest thing to a productivity magic wand that I could hope for.</p><p>Here’s how I’ve seen it work:</p><p>The team knows someone junior is about to join. You assign someone more senior to make a bit of a plan for when they join. That person looks at the onboarding file in your git repository and finds it woefully out of date: it is missing important things, the commands dont run, it’s talking about team practices that you don’t do anymore. They panic because they know this next person can’t just use their experience to struggle their way out of the problem like the last 3 joiners did. They fix the document, and now you’re more resilient to hiring new people.</p><p>The new engineer joins. They go through the onboarding. The team knows they are more junior, so rather than assuming they figured it out somehow, they ask how it went. Now you’ve got a team actually getting user feedback about your onboarding process.</p><p>The new engineer asks what a “sprint planning meeting” is for. It turns out nobody knows what it is for. The team replaces it with a weekly Slack thread and you get an hour per fornight back.</p><p>An architectural change is made. The very senior person who drove the change knows that it relates to a feature that the new engineer is working on, so they call an all hands to explain how it works. They can’t put it into words, so the day before the all hands they ask for advice from somebody who is good at explaining it. The team gets a good explanation of the change, and the senior engineer has had an experience that will make them consider prioritising investing in their own communication skills.</p><p>In short, a cultural pressure to improve communications was created: by adjusting to the needs of one person, your team ended up doing things that worked better for everybody.</p><h3>2. Seniority is not a safety strategy</h3><p>The risk of letting less experienced people near your codebase is not as high as the risk you are already running by allowing all-senior teams to exist in your organisation.</p><p>Saying your quality strategy depends on everybody being an accomplished expert with years of experience is like saying your fire safety strategy depends on you always renting your spare room to a firefighter.</p><p>What defects in your processes are being hidden by the fact that everybody <em>just knows better? </em>Your all star team are going to slip up at some point, no matter how brilliant they individually are. They might ssh into the wrong box and drop a production db, spend 3 months building something that it turns out is pointless, or not appreciate the nuance of a data privacy law and get you sued. Your processes won’t be there to guard against these mistakes, because you wanted to avoid the early pain of figuring out what processes make it safe for everybody to contribute.</p><p>Put another way, if it’s painful do it more often.</p><p>Quality is made unstable in exactly the same way. “We’ll just always hire the most experienced people” is not a predictable way to do good work. You might be able to rely on this if you can consistently and substantially outbid your competitors for salaries <strong>and </strong>you have a reputation as one of the best places in the world to work. But realistically, you don’t have that. If you think you do, you probably haven’t done enough user research on your applicant pool.</p><p>If I had to bet on the team that would produce the best product, it wouldn’t be the team that refuses to hire anybody without a decade of experience, it would be the team that:</p><ul><li>Recognises a vast array of different strengths when hiring, and makes plans to reorganise itself to utilise those strengths.</li><li>Invests regularly in training.</li><li>Uses systems thinking to iterate on its own processes, driven by data about outcomes.</li></ul><h3>Doing it right</h3><p>All that said, this isn’t free. You’ve got to do it right. If you try to introduce mixed seniority teams but you don’t have a plan, a support structure, a good cultural foundation that rejects blame and values learning, and some realistic expectations you’re going to be burned. If you’re interested in this, drop me a message on <a href="https://twitter.com/rbs_tito">Twitter</a>, I might write up what I’m doing on this front over the next few weeks.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eacb98f185d1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Lessons learned from building a government service]]></title>
            <link>https://rbs-tito.medium.com/lessons-learned-from-building-a-government-service-883dcc8d8f24?source=rss-4d05b4515d6------2</link>
            <guid isPermaLink="false">https://medium.com/p/883dcc8d8f24</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[digital-transformation]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Tito Sarrionandia]]></dc:creator>
            <pubDate>Sun, 03 Jan 2021 00:06:51 GMT</pubDate>
            <atom:updated>2021-01-03T00:06:51.115Z</atom:updated>
            <content:encoded><![CDATA[<p>Last year, I was fortunate enough to spend some time with <a href="https://www.gov.uk/government/organisations/ministry-of-housing-communities-and-local-government">MHCLG </a>as the technical lead on a project to replace the ageing Energy Performance of Buildings Register. Kev Keenoy has written a <a href="https://mhclgdigital.blog.gov.uk/2020/05/19/rebuilding-the-energy-performance-of-buildings-registers/">good summary of the work</a>. The project is now live and serving citizens across England, Wales, and Northern Ireland.</p><p>I’d worked in government before, but this was the first time I got to see a central government project through from inception to go-live. I held a personal retrospective to capture some important feelings that I wanted to explicitly write down somewhere.</p><p>Here are my main (entirely unoriginal) thoughts, which might be useful to people taking on their first digital leadership position in the UK government.</p><h3>Policy as urban legend</h3><p>I spent a lot of time worrying about policy that didn’t exist. That sounds mad, but I suspect there are many teams in government doing the same thing.</p><p>It helps to understand what people mean when they say <em>policy</em> on a digital government team. They can mean a number of things:</p><ul><li>Legislation passed by parliament</li><li><a href="https://www.parliament.uk/site-information/glossary/delegated-or-secondary-legislation/">Secondary legislation</a></li><li>Documents that make some sort of commitment to internal or external stakeholders.</li></ul><p>I think it is easy to assume that the things people tell you are policy are mostly legislation, but when you dig into it they are often just internal documents. Policy documents can be found to articulate any number of decisions that you might assume would be too low level for somebody concerned with “policy” to care about. Actual examples of real policies I have come across in the wild are:</p><ul><li>What members of staff will <em>wear </em>in citizen facing roles.</li><li>That there will be a “button” on a page allowing the user of the page to filter their search results.</li></ul><p>In short, they are the artefacts from the Civil Service’s unique culture of making decisions through essay writing contests. The upshot of this is that many of the things I assumed were intractable restrictions turned out to be easily-ish overturned.</p><p>Additionally, many of them <em>simply didn’t exist. </em>People will tell you with full confidence that a particular policy is restricting your choice in some way: it is your team’s job to figure out exactly what they are talking about, because sometimes the trail runs cold and you learn the policy is an urban legend.</p><p>I first noticed this when GDPR was introduced, I was working for a different part of the government (which I won’t name) and senior people would confidently make absurd statements about some particular implication of GDPR on our work. Those are repeated in meetings and emails and start to take on a life of their own.</p><p>Compliance is important for government teams, it’s a line you can’t cross, but cultures of compliance have a nasty habit of weaponising knowledge of policy to avoid important decision making. Not always, but occasionally, you’ll find that “it’s policy” is the government equivalent of “they’re the requirements”: a phrase which <a href="https://www.oreilly.com/library/view/user-story-mapping/9781491904893/">Jeff Patton observed </a>really means “shut up”.</p><h3>Service owner as sceptic</h3><p>We started the project without a full time service owner, but when one joined it made a massive difference. Having a service owner who understands that some policies don’t exist and how policies that do exist can change is the only way around this. Our service owner knew this and cut short our journey into a number of rabbit holes that would ultimately have sabotaged launch had we pursued them.</p><p>I now see a good service owner as being like Adam Connover from Adam Ruins Everything. They must be the person who knows the facts and isn’t afraid to introduce them, even when it’s socially inappropriate. A well timed “Actually, the legislation only says…” is priceless.</p><p>The service owner needs to help you pick your battles. If I could change one thing about the project at MHCLG, it would be to fill the service owner role right from the beginning and frame the whole thing around a realistic timeline of decision making and political challenges.</p><h3>Keep expectations high</h3><p>You can build high performing engineering teams in government. Contrary to popular belief, you do not need scores of engineers with glittering CVs and a truck full of venture capital to achieve <a href="https://services.google.com/fh/files/misc/state-of-devops-2019.pdf">all of the things that we know work</a>.</p><p>My team was a small team of mixed seniority, the type of experience mix that you’ll easily find in every government department. They built a process that could release to production 50 times every day, where the lead time (between committing code and that code being used by an external user) hovered below 15 minutes, where all infrastructure was defined in source code and completely replaced on each release. Stories went from being accepted to being completed in predictable time frames. The team was consistently open about their own abilities and performance, and had each others backs.</p><p><em>I’m extremely proud of how we managed to do that with an unremarkable budget and a team with multiple junior members.</em></p><p>As I entered the orbit of the civil service, I was told multiple times that none of this was possible. Because of more mythical policies about how crucial pull requests are (<a href="https://infrastructure-as-code.com/book/2021/01/02/pull-requests.html">they aren’t</a>), but even worse because of a perceived skill gap between the public and private sector.</p><p>But the highest performing teams don’t work well because they self select for prestige, they work well because they create the conditions where actual people who exist in the real world can safely achieve more.</p><p>I’ve got opinions about what high performance looks like (continuous integration, test driven development, intense collaboration, diversity, safety in software changes, psychological safety, outcome driven, empathy, etc.) — but I don’t really want to make this into generalised advice about what high performing means.</p><p>I do want people to have the confidence to fight back against excuses for low expectations and aim for something that lets people experiment and get better results. I’m grateful that <a href="https://www.madetech.com/">Made Tech </a>(my employer at the time), gave me the freedom to pursue this without compromise.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=883dcc8d8f24" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[It’s not Google Duplex, it’s you]]></title>
            <link>https://rbs-tito.medium.com/its-not-google-duplex-it-s-you-7c5bee2dac96?source=rss-4d05b4515d6------2</link>
            <guid isPermaLink="false">https://medium.com/p/7c5bee2dac96</guid>
            <category><![CDATA[google-duplex]]></category>
            <category><![CDATA[google]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[ethics]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Tito Sarrionandia]]></dc:creator>
            <pubDate>Sun, 13 May 2018 12:00:14 GMT</pubDate>
            <atom:updated>2018-05-13T12:00:14.527Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/240/1*NXp55b7-Wt7-sdEgUO2V_A.png" /><figcaption>He would use Duplex</figcaption></figure><p>In Asimov’s Robot series, several societies uphold the custom that robots must introduce themselves with the prefix “R”. For example, Daneel Olivaw, the humaniform robot so convincingly lifelike that it can deceive most actual humans, introduces [it/him]self as R. Daneel Olivaw.</p><p>If you’re not particularly interested in tech ethics, you’ve probably seen the video of Google’s AI assistant making a convincing phone call on behalf of its human owner to book a haircut, a technology they are calling Duplex. If it really works as well as the demonstration, it’s pretty incredible.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FD5VN56jQMWM%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DD5VN56jQMWM&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FD5VN56jQMWM%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/115aced490f45d8f5a5bca2538b706ac/href">https://medium.com/media/115aced490f45d8f5a5bca2538b706ac/href</a></iframe><p>If you are interested in tech ethics, you’ve probably also seen a take like this one from CNET’s Bridget Carey.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FY0otgRmscUk%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DY0otgRmscUk&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FY0otgRmscUk%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/a567ffcafa910bab21bc6bfca82eedbe/href">https://medium.com/media/a567ffcafa910bab21bc6bfca82eedbe/href</a></iframe><p>Bridget (and everyone else on YouTube) identifies the primary ethical issue as being the same one identified by Asimov: that human beings have a right to know when they are and aren’t interacting with other human beings.</p><p>I think this is far fetched. If you’ve ever used Twitter you probably know that ship has sailed, and if anything this technology makes me think that voice calling as a format will die a slow death as the number of humans making calls shrinks compared to the number of robots making sales, research, and political calls, and restaurants get a few bad experiences with empty tables caused by unclear conversations with robot assistants of varying quality. Especially since it sounds like the production version will identify itself somehow during the call.</p><p>That’s a shame, because there is an ethical issue here, it’s just not the kind of broad, scary, political ethics that we’re used to AI invoking, instead it’s just about good manners.</p><p>Unlike in Asmimov’s world, we aren’t used to talking to robots as if they are people. The robots also don’t really have any agency in our world — at least not the ones we interact with, yet.</p><p>Ignore AI planetary takeovers, my problem is this: If you use Duplex to interact with another human, at least for the foreseeable future, you are an arsehole. Every time I see you I will be thinking about Michael Scott or Alan Partridge.</p><p>First, you’d better be pretty damn sure this technology is perfect before you unleash it on somebody else. If your robot phones me up to make an appointment and I have to repeat myself, or it is unclear whether or not you have booked, you are no longer optimising your own time, you are just stealing mine.</p><p>Even if things do go smoothly, if I know I’m talking to a robot over the phone — either because I come to recognise the voice, or it introduces itself to me — it is going to be incredible embarrassing for me to have that conversation. I have to choose whether or not to talk to it like a human or like I talk to my own voice assistant.</p><p>I can either keep up the facade and waste even more of my own time asking it about the weather and wishing it well, like an idiot, or I can start barking commands down the phone, which is something I am not willing to do if other people, even strangers, are in earshot. I don’t even use the voice assistant on my own phone if there is a single other person in the room because it’s kind of outside the social norm, and yet I have to suffer the same embarrassment to save somebody else’s time? That’s rude.</p><p>Google, of course, has done this before. Glass was kind of a cool project, I really liked the idea of maps overlays into your vision and taking photographs without taking out my phone. It would make sense in a society where people had normalised the new interactions it introduced, but in this society it was <a href="https://www.theguardian.com/technology/2014/dec/03/google-glass-review-curiously-useful-overpriced-socially-awkward">just too much</a>.</p><p>It’s weird that you can’t tell if somebody is taking a photo of you. You also force the issue of using screens in company. Using phones over dinner seems just about socially acceptable now, if you look around any café it’s hard to avoid that conclusion, but there’s still a little bit of social theatre required to pick the right moments. If someone is opening up about something to you, you had better put your phone in your pocket. Having the screen affixed to your face didn’t allow for that subtlety. Just wearing Google Glass was impolite. Maybe in 10 years people will care less.</p><p>I just about accept that some people are too busy to make their own hair appointments. If your time is incredibly valuable then maybe that 120 second call is really worth converting to a 15 second instruction to a PA. However, you must accept that by doing so you are sending out a very clear message about how much you value your own time.</p><p>Namely, it is worth paying somebody a salary to make a 105 second saving for trivial admin tasks. My time isn’t worth anywhere near that, and neither is yours. I know this because I wrote this post, and you are reading it.</p><p>Clearly the cost of a robot assistant is much lower than a human one to the point that maybe, in 10 years, using assistants won’t carry this connotation, but for now it absolutely does. You still think it’s worth making that 105 second saving every 5 weeks, you still think that’s worth the extra time and embarrassment for the recipient of the call. You just are unable or unwilling to pay for it.</p><h3>Tito Sarrionandia on Twitter</h3><p>Do you believe your time is too valuable to make your own haircut appointment, but have failed to convince anyone else in the world of your value so don&#39;t have a PA? Google has the product for you.</p><p>I get that we might move fairly quickly to the point where enough of these conditions have changed. Assistants are reliable, we don’t feel stupid asking robots how their day has been, it’s not considered self important for me to outsource my small admin tasks to something else while spending my Sunday watching YouTube clips — but until that happens:</p><ol><li>Don’t get your robot to phone me</li><li>Maybe just sign up to OpenTable?</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7c5bee2dac96" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What I learned from getting rid of most of my possessions]]></title>
            <link>https://rbs-tito.medium.com/what-i-learned-from-getting-rid-of-most-of-my-possessions-173d0de937b0?source=rss-4d05b4515d6------2</link>
            <guid isPermaLink="false">https://medium.com/p/173d0de937b0</guid>
            <category><![CDATA[minimalism]]></category>
            <dc:creator><![CDATA[Tito Sarrionandia]]></dc:creator>
            <pubDate>Sat, 06 Jan 2018 15:24:06 GMT</pubDate>
            <atom:updated>2018-01-06T15:25:01.206Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nfKIRG2LZFnJzSa1jTIwqQ.jpeg" /></figure><p>I travel <strong>a lot</strong> for work. Last year I traveled in excess of 300 days. For all of that time I was renting a place in central London, and it was a pretty great place. It was a short walk from everything I like to do in London, and I shared it with one of my favourite people in the world. Still, I’m never there, and it’s a crazy waste of money, so I’m giving it all up in favour of less expensive accommodation and (in practice) living out of a single suitcase wherever work might take me.</p><p>This means getting rid of a lot of stuff, I’d say upwards of 90% of the stuff I have. I learned more about myself from doing this than maybe any other activity I’ve ever done. Here are some random thoughts and pains that came to me while I was doing it.</p><p>Also, I get this a pretty boujie exercise, more Edina Monsoon than enlightened ascetic. You can probably only do this safely if you have a pretty decent safety net of family, friends, and finances to fall back on. But it works for me right now.</p><p>Clothes are basically pathologies for me. Some of the hardest things to throw away were clothes, because they were go-to outfits for things I don’t really do anymore (oh hey university debating society hoodies), or because I had a really good night out in them once. Do I go to enough parties to warrant taking up space in my suitcase for five different sequin covered outfits? Nope. Am I likely to need to put on a three piece suit and a bow tie to teach kids again? Nope. Do I go to parties wearing black tie anymore? Nope. It’s hard to accept that I’m a different person who does different things now, but getting rid of an outfit belonging to a previous version of me is the final nail in the coffin of a lifestyle change, and makes me realise I don’t really have the self confidence to be certain I’ve made the right choices about how I want to spend my time in 2018.</p><p>Books are mysticism. I have this box of books which basically functions as a tabernacle. I carry it from new house to new house, never actually opening it to read the books inside, because I’ve already read them. But my head is filled with nonsensical ideas about books. I need physical books to belong to the club of intellectuals, they are also somehow sacred and can’t be subject to the insult of being damaged or recycled, and finally it’s hard to distinguish accepting that I no longer need the physical item from saying that I no longer need what’s written inside it. Like, how can I be a good software developer if I throw away the <a href="https://en.wikipedia.org/wiki/Design_Patterns">Gang of Four</a> book? Am I really still an atheist if I throw away Bertrand Russel? There are a three or four books that have some other value to me, and I’ve kept those in a much smaller box, but the rest have been sold and recycled. I’ve also blown the dust off my Kindle, which I’ve grown to love again.</p><p>Things for entertaining guests that don’t exist at parties I don’t throw are also fairly hard to get rid of. Serving people is kind of second nature to me, growing up in a hotel, and I think I buy things as if I am going to be living in and running a hotel. I really don’t need enough martini glasses to throw a cocktail party, I’ve literally never thrown a cocktail party in my life. I don’t need cake tins, or muffin trays, or any of this stuff. Still, I feel like I <strong>should</strong> be entertaining guests, it feels like it’s the done thing. Getting rid of this stuff means that I can’t spring into action with a round of mimosas when the need arises, which is something I’d like to think I would do.</p><p>Gifts are also pretty hard, and they mostly cross categories. The majority of the things I own were gifts at some point or another. It’s hard to get rid of a gift without feeling like you’re getting rid of the person who gave it to you. My cupboards are full of gifts I’ve not used once. I really appreciated those gifts when they were given to me — or, more specifically, I appreciated the fact that someone would choose to give me a gift — but the gift itself rarely fits into my life. I’m lucky enough to have enough money to just buy something when I want it. Still, this is all obvious nonsense, and I should probably just be better at communicating what I do not need when birthdays and Christmases come around. These were actually the most liberating things to get rid of, because seeing them in the back of the cupboard made me feel guilty for not needing it every time I looked.</p><p>Lastly, I’m learning to deal with carrying digital copies of sentimental things. I have a box of thank you cards from my students back in Birmingham. I have taken photos, and I’m sure I’ll look at these way more often than the paper copies. I also now have no real fear about losing or damaging them.</p><p>Mostly I now feel like I have the things that fit the things I actually want to do in 2018. I want to build some tech, spend my free time going for walks and reading sci-fi, and I’m now more likely to be hanging out at a cabaret dive bar than the Savoy. It’s not quite ageing gracefully, but it’s probably as close as I’ll get.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=173d0de937b0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Was Teach First worth it?]]></title>
            <link>https://medium.com/education-reform/was-teach-first-worth-it-b69a8634074a?source=rss-4d05b4515d6------2</link>
            <guid isPermaLink="false">https://medium.com/p/b69a8634074a</guid>
            <category><![CDATA[education]]></category>
            <category><![CDATA[teaching]]></category>
            <category><![CDATA[teach-first]]></category>
            <dc:creator><![CDATA[Tito Sarrionandia]]></dc:creator>
            <pubDate>Fri, 17 Jul 2015 14:10:42 GMT</pubDate>
            <atom:updated>2015-08-05T19:31:20.550Z</atom:updated>
            <content:encoded><![CDATA[<p>I’ve just finished the last week of my job as a computer science teacher on the Teach First leadership development programme. I won’t be returning to the classroom next year, instead I’ve accepted a position in the software industry. The past two years have undoubtedly been the most difficult of my life. When I tell people about my current lifestyle, they always ask the same question: “Is it worth it?”</p><p>Teach First is a charity that aims to bring about an education system in the UK that doesn’t allow people’s socio-economic background to limit their success. The main way by which it tries to achieve this is by acting as a recruiter for state schools, creating an elite graduate scheme that gives you teacher training, postgraduate university education, professional training, and career opportunities in return for two years of your labour in a state school in challenging circumstances. If you saw the BBC 3 series “Tough Young Teachers”, you’ll know a little about how that works.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FA-4lNdyYSAI%3Ffeature%3Doembed&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DA-4lNdyYSAI&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FA-4lNdyYSAI%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/6c033d1b5496e5aebd30ba6c97c5f9b5/href">https://medium.com/media/6c033d1b5496e5aebd30ba6c97c5f9b5/href</a></iframe><p>Teach First goes to great lengths to avoid being seen or described as an avenue for graduates to swoop into and fix the broken education system on their way to a more lucrative job in the city, and to that end it tries to recruit people who possess some measure of humility. That’s important: There is a lot that works well in the education system, and it is the dedicated professionals with years of experience that do the lion’s share of the work in schools.</p><p>Despite this, there’s something obviously appealing about the idea of making a difference. Teach First is the biggest graduate recruiter in the country, and it certainly isn’t the money that draws those graduates in. Participants start on the unqualified teachers’ pay scale. Teachers usually get a pay rise once per year, as long as they meet their performance targets, so achieving a good salary is mostly a waiting game. You can get extra pay if you are awarded extra responsibilities (such as an academic or pastoral leadership position), but these too start off small, and whether or not you are likely to be given one depends on the internal politics of the school you have been (almost randomly) dropped into.</p><p>Neither is the lifestyle much of a draw. If anyone starts Teach First under the impression that they would be able to leave work at 3pm and enjoy their evenings, they probably don’t stick around for very long. I have seen the inside of the school building after midnight, worked more weekends than I’ve taken off, taught extra classes during school holidays, and spent every hour that I am not working feeling guilty about the work that I should be doing.</p><p>I should stress that I don’t think I’ve really gone above and beyond. I’ve run a few small projects on the side and dabbled in some extra curricular things, but the hard work is mostly a function of trying to complete my core tasks on time. That is to say the tasks that, should they go uncompleted, will leave people annoyed and questioning my competence.</p><p>The gist of it is this: Each day you need to teach 3–5 hour long lessons to a room full of between 10 and 30 children. These lessons are expected to be something like a performance, and as such require a lot more energy than a university lecture or a business presentation. I walk around the room, construct elaborate demonstrations, spin metaphors, try to model my thought process as I solve problems, ask questions, and answer questions.</p><p>On top of that, the audience is sometimes semi-hostile. Your job is also to persuade the baying mob to transform into five rows of neatly organised, smartly presented and productive young people. This involves winning them over with interesting insights, taking time out to share your (partially genuine and partially pragmatic) thoughts on morality and character development, altering the seating arrangements, calling parents, and occasionally being more confrontational than my British sensibilities should allow.</p><p>In addition to delivering the lessons, you need to plan for them, create resources, mark the students’ work, issue and follow up on sanctions and praise, and be in constant communication with parents. There is also a stream of tasks turning up in your email inbox that are sometimes bizarre (creating a song about healthy eating), sometimes tedious (sending a letter to 20 parents), and often totally outside of my skill set (redecorating a classroom).</p><p>I don’t mean to put too much emphasis on the high demands of the profession, that’s true of most professions and the whole thing was quite fun, just to put to bed the idea that one would take up teaching for the easy life.</p><p>Teaching didn’t furnish me with a good salary or a relaxed lifestyle. In fact it is, by some distance, the most significant investment of energy and emotion that I have ever made. So what did I get out of it?</p><p>I think I might have made a difference in some small way, albeit in the trivial and non-ambitious sense of the word.</p><p>It’s true that I can point to particular students and see progress. My first class of 15 boys had never heard of a compiler, and are now mostly competent software developers. I invested significant time, thought and care into a student who was constantly failing to meet expectations, and saw him turn into someone who only occasionally fails to meet expectations.</p><p>These things feel good emotionally, they are stories about real people who I think will go on to do good work and who I hope will remember me from time to time. Yet a rational observer would have to keep in mind that <strong>any</strong> educator should have achieved these things if they were semi-competent. If a computer science teacher can’t teach children how to program, they are a failure. The emotional return on this investment is high because I am working with children instead of a production line or at the code face, and I’m content with that, but it’s not amazing or unique.</p><p>The more ambitious sense of making a difference, of making systemic changes that go beyond the effects caused by your direct manipulation, is much more difficult to achieve. There are <em>definitely</em> ample opportunities for you to do this in education, and I’ve spent the past two years inspired by people like Daisy Christodoulou and Katharine Birbalsingh who are doing just that.</p><p>If you intend to make that sort of a difference, you need to be prepared to stick at this thing for much longer than I have. With that said, those avenues aren’t totally closed off to me now, I’d gladly consider working with or for one of the many charitable and voluntary sector organisations that are doing excellent educational reform work.</p><p>The main return on my investment, and the thing which I think means I can say it was worth it, has been the opportunity to learn.</p><p>Teach First is an intense experience which requires you to muster a lot of perseverance and emotional intelligence in ways that most university students won’t have come across before. Two years ago I could never have kept calm and composed while a 13 year old discloses harrowing information about his personal life; turned around 20 students who are too demotivated to work; reassured a a colleague going through a hard time; expressed my disappointment and disapproval, or appreciation and praise, to a room full of people; broken up a fight; or helped somebody to work through their confidence issues. These are all things that I don’t think many other jobs would drop you in to, but I can safely say that I’m now alright at them. You awkwardly fumble your way through it at first, but it gets easier.</p><p>I also know a lot more about myself. I know my limits, I know my coping strategies, and I know which parts of my life are non-negotiable.</p><p>I know a little bit about teenagers now too. Before Teach First, they were angry and unpredictable misanthropes who can’t communicate and smell awful. They still smell bad, but you get to see them flourish and show off their strengths, and help them with their issues — which, contra awful stereotypes, are real issues — as they turn into better people. That sounds rosy, and of course lots of them make poor moral choices. Many of them won’t succeed, but some will, and I’ve got a better idea about what that path to success looks like.</p><p>I also know more about the world around me. The education system is strange and in many ways messed up. We entrust the vast majority of the children in the country to this system — and not just for their academic progress — schools have become institutions entrusted with keeping children safe, managing their relationships, building their expectations and aspirations, and developing their character. They are immeasurably important. It works for lots of children, but not for all, and especially not for the most vulnerable.</p><p>My final answer to this question has changed as we have gone through the highs and lows of the school year, but reflectively it is <strong>yes.</strong> It is absolutely worth it.</p><p>If you’ve made it through university and are in a position to apply for Teach First, or to access the education system through some other route, you are in the minority. The education system probably served you very well, or at least didn’t totally destroy your future. Go and see how it treats everybody else, and do some good work on the way.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b69a8634074a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/education-reform/was-teach-first-worth-it-b69a8634074a">Was Teach First worth it?</a> was originally published in <a href="https://medium.com/education-reform">Education Reform</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>