<?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 Alice Bartlett on Medium]]></title>
        <description><![CDATA[Stories by Alice Bartlett on Medium]]></description>
        <link>https://medium.com/@alice.bartlett?source=rss-5872a7f3d90a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*vAQtP_BwYbSPdWVl.jpg</url>
            <title>Stories by Alice Bartlett on Medium</title>
            <link>https://medium.com/@alice.bartlett?source=rss-5872a7f3d90a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 14:22:19 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@alice.bartlett/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[A New Framework for Engineering Progression at the FT]]></title>
            <link>https://medium.com/ft-product-technology/a-new-framework-for-engineering-progression-at-the-ft-af7c909252fe?source=rss-5872a7f3d90a------2</link>
            <guid isPermaLink="false">https://medium.com/p/af7c909252fe</guid>
            <dc:creator><![CDATA[Alice Bartlett]]></dc:creator>
            <pubDate>Mon, 17 Nov 2025 11:23:10 GMT</pubDate>
            <atom:updated>2025-11-17T11:25:43.638Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*QSgPwP0IHIhN-vNGtf_MCA.png" /></figure><p>At the Financial Times, we’ve recently updated the career framework for our engineers and managers. It’s clearer, simpler and more practical for our teams and for anyone thinking about joining us. In this post, we’ll talk about why we made the change, how it works and what we hope it will do.</p><h3>Why We Changed It</h3><p>We <a href="https://medium.com/ft-product-technology/improving-our-career-map-for-engineers-4210185c6246">introduced our first structured progression framework</a> (the predecessor to this one) in 2019. It replaced a messy set of spreadsheets and helped bring clarity to how we described engineering roles and the requirements to demonstrate progression. But five years on it’s clear that the framework needed an update for the following reasons:</p><ul><li>The old framework had too many items and felt like a checklist.</li><li>It didn’t clearly separate technical and people leadership, or provide a choice for career direction.</li><li>It was hard to keep current, because of a focus on technical skills and processes rather than broader competencies.</li><li>It didn’t explain how engineering connects to business outcomes.</li><li>It didn’t include Operations roles, or our most senior roles, Principal Engineer and Tech Director.</li></ul><h3>What’s Different Now</h3><h4>Two Career Paths</h4><p>We now support two distinct ways to progress:</p><ul><li><strong>Individual Contributors (ICs)</strong> focus on technical work and impact.</li><li><strong>People Managers</strong> focus on helping others grow, building strong teams, and creating the conditions for people to do their best work.</li></ul><p>Engineers don’t need to become people managers to progress. It’s possible to grow careers through IC roles all the way to Principal Engineer.</p><h4>Simpler Structure</h4><p>We’ve gone from 80+ competencies to just nine:</p><ul><li>Planning and Organising</li><li>Independent Working</li><li>Problem Solving &amp; Decision Making</li><li>Business Impact</li><li>Communication</li><li>Team Work</li><li>Curiosity &amp; Learning</li><li>Leadership of Self and Others</li><li>Technical</li></ul><p>Each competency describes behaviours we value and the impact we expect at each level in the career path.</p><h4>Focus on Impact</h4><p>We’re now more interested in the behaviours people demonstrate consistently and the impact they have, than whether they’ve ticked off items on a list. This means more room for engineers to shape their own growth, depending on their role, interests, and strengths.</p><h4>Support for Career Decisions</h4><p>The new framework gives clearer guidance on how to progress. It helps engineers and managers have better conversations about current performance and future development, and makes it easier to perform an IC role or a People Manager role as these are now separately defined.</p><h4>How We Built It</h4><p>This framework was developed by our engineering leadership team with support from FT People, our HR team, with feedback from across the technology team. We also looked at how other organisations approach progression, and spoke to engineers, managers and product people across the FT to understand what they needed from a framework.</p><h4>Why We’re Sharing It</h4><p>Our progression site remains publicly viewable. Over the years countless job applicants have told us that being able to see our framework helped them prepare for interviews with us and understand what working at the FT is like.</p><p>If you’d like to see how we think about engineering careers (or borrow some ideas) we’ve made everything available at<a href="https://engineering-progression.ft.com/"> engineering-progression.ft.com</a>.</p><p><em>Take a look:</em><a href="https://engineering-progression.ft.com/"><em> engineering-progression.ft.com</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=af7c909252fe" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ft-product-technology/a-new-framework-for-engineering-progression-at-the-ft-af7c909252fe">A New Framework for Engineering Progression at the FT</a> was originally published in <a href="https://medium.com/ft-product-technology">FT Product &amp; Technology</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Pragmatic Programmer book club finale]]></title>
            <link>https://medium.com/ft-product-technology/the-pragmatic-programmer-book-club-26d25f4e59d0?source=rss-5872a7f3d90a------2</link>
            <guid isPermaLink="false">https://medium.com/p/26d25f4e59d0</guid>
            <category><![CDATA[engineering-book-club]]></category>
            <category><![CDATA[pragmatic-book-club]]></category>
            <category><![CDATA[pragmatic-programmer]]></category>
            <dc:creator><![CDATA[Alice Bartlett]]></dc:creator>
            <pubDate>Wed, 04 Jan 2023 13:38:33 GMT</pubDate>
            <atom:updated>2023-01-04T13:43:22.749Z</atom:updated>
            <content:encoded><![CDATA[<p><a href="https://medium.com/ft-product-technology/book-club-the-pragmatic-programmer-2886fe053ef">Back in August</a> I wrote that we had started a book club to meet more of my colleagues and we that were going to read the 20th Anniversary re-release of The Pragmatic Programmer.</p><p>I wanted everyone to read an hour a week, and chat for 45 minutes. That seemed manageable within people’s work week and I didn’t want anyone to have to fit this in outside of work.</p><p>We had 10–20 people attend each week, which was helped along by the fact that the book is discrete chapters which you can read without having done any previous reading. Numbers started high, eventually settling to around 12 regulars.</p><p>I wrote up the questions I had around each chapter on my personal medium but I didn’t want to spam all of our FT product and tech blog readers with such niche content. At the bottom of this post there’s a list of all of the chapter write-ups.</p><h3>Is this book any good?</h3><p>Yes? No? Some of it is good. I think it’s handy to have a broad explanation of concepts many of us practice now without thinking.</p><p>Being reminded of <em>why</em> we do stand-ups or version control or whatever is pleasant. The fact that some of the coding concepts in this book don’t exist in JavaScript led to some very interesting conversations about different programming languages and preferences.</p><p>I think my main beef with the book was the heavy use of metaphors that just felt a bit… American? Boomery? These metaphors got in the way because they didn’t resonate with the diverse readership in the book club.</p><h3>It was the friends we made along the way</h3><p>Of course, the point of this book club was actually to meet some of my colleagues and have some weak socialising around a single topic we could all contribute to. And that happened. Everybody who made it to the end (about 12 regulars) agreed that the conversations about each chapter were the best thing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*f2EPkaJUE8ztUd63VQo-Pg.jpeg" /><figcaption>Artist’s impression of the book club. Image Credit: <a href="https://medium.com/u/e7626ad3cec2">Rowan Manning</a></figcaption></figure><h3>Start a book club — use my notes!</h3><p>An important part of work is talking to your colleagues. There are lots of ways to do this, but many of them work better for people who are very outgoing, or are co-located. When I started this book club it seemed like I could create a point in time where people could meet, and give those people a thing to talk about that they could prepare for. Bonus — the topic of conversation was work related but not actually the work.</p><p>If you want to repeat this experiment at your work then I think the Pragmatic Programmer is an easy book to do it with, and you can even use my write-ups (linked at the bottom) to help with your own discussion points. Let me know if you do this!</p><h3>We’re going to go again in 2023</h3><p>We’ve already had some suggestions for which book to choose next, but we’re going to have a little rest over winter before we make any decisions. ✌️</p><h3>Chapter write ups</h3><ul><li><a href="https://medium.com/ft-product-technology/book-club-the-pragmatic-programmer-2886fe053ef">Book Club: The pragmatic programmer</a></li><li><a href="https://medium.com/@alice.bartlett/pragmatic-book-club-meeting-0-house-keeping-f22294c24d20">Pragmatic Book Club meeting 0: house keeping</a></li><li><a href="https://medium.com/@alice.bartlett/pragmatic-book-club-chapter-1-ccd20e904839">Pragmatic Book Club: Chapter 1</a></li><li><a href="https://medium.com/@alice.bartlett/pragmatic-book-club-chapter-2-3aea0282e53a">Pragmatic Book Club: Chapter 2</a></li><li><a href="https://medium.com/@alice.bartlett/pragmatic-book-club-chapter-3-c4b574d8b1b7">Pragmatic Book Club: Chapter 3</a></li><li><a href="https://medium.com/@alice.bartlett/pragmatic-book-club-chapter-4-97304a2abdd1">Pragmatic Book Club: Chapter 4</a></li><li><a href="https://medium.com/@alice.bartlett/pragmatic-book-club-chapter-5-f5a0486951bb">Pragmatic Book Club: Chapter 5</a></li><li><a href="https://medium.com/@alice.bartlett/pragmatic-book-club-chapter-6-b7de05d4b5f2">Pragmatic Book Club: Chapter 6</a></li><li><a href="https://medium.com/@alice.bartlett/pragmatic-book-club-chapter-7-5e8267fa26d6">Pragmatic book club chapter 7</a></li><li><a href="https://medium.com/@alice.bartlett/pragmatic-book-club-chapter-8-32e5dbcef190">Pragmatic Book Club: Chapter 8</a></li><li><a href="https://medium.com/@alice.bartlett/pragmatic-book-club-chapter-9-98e720e9050a">Pragmatic Book Club: Chapter 9</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=26d25f4e59d0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ft-product-technology/the-pragmatic-programmer-book-club-26d25f4e59d0">The Pragmatic Programmer book club finale</a> was originally published in <a href="https://medium.com/ft-product-technology">FT Product &amp; Technology</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Pragmatic Book Club: Chapter 9]]></title>
            <link>https://medium.com/@alice.bartlett/pragmatic-book-club-chapter-9-98e720e9050a?source=rss-5872a7f3d90a------2</link>
            <guid isPermaLink="false">https://medium.com/p/98e720e9050a</guid>
            <category><![CDATA[engineering-book-club]]></category>
            <category><![CDATA[pragmatic-book-club]]></category>
            <category><![CDATA[pragmatic-programmer]]></category>
            <dc:creator><![CDATA[Alice Bartlett]]></dc:creator>
            <pubDate>Thu, 15 Dec 2022 13:46:00 GMT</pubDate>
            <atom:updated>2022-12-15T13:46:00.190Z</atom:updated>
            <content:encoded><![CDATA[<p>This book ends with <em>Pragmatic Projects. </em>This chapter kind of pulls together bits from the previous 8 chapters into a full project view. As a group we weren’t super into this chapter, it felt like a wrap up rather than something that was bringing any new ideas.</p><p>Nobody loved the coconuts don’t cut it bit. Once again, Dave and Andy, call me before you release the next edition. I’ll tell you all the bits that make you sound racist.</p><blockquote>Find bugs once</blockquote><p>YES. Couldn’t agree more.</p><p>We got into quite a long discussion about what Dave and Andy meant by “sign your work” or if that was just an excuse to shoehorn in their own signatures at the end of the book.</p><p>We also read the postface this week. It was good to talk as a group about what our ethical obligations are and the times in which we have spoken up when something has seemed a bit questionable. As recently as this year I have questioned some 3rd party software that felt like it was overreaching in terms of privacy, only to realise lots of others also felt a bit weird about it but were waiting to see if anyone else was going to say anything.</p><p>OK that’s the end. Nine chapters and a postface.</p><p>Next blog post will be a round up and overall review. Byeeee.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=98e720e9050a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Pragmatic Book Club: Chapter 8]]></title>
            <link>https://medium.com/@alice.bartlett/pragmatic-book-club-chapter-8-32e5dbcef190?source=rss-5872a7f3d90a------2</link>
            <guid isPermaLink="false">https://medium.com/p/32e5dbcef190</guid>
            <category><![CDATA[pragmatic-programmer]]></category>
            <category><![CDATA[pragmatic-book-club]]></category>
            <category><![CDATA[engineering-book-club]]></category>
            <dc:creator><![CDATA[Alice Bartlett]]></dc:creator>
            <pubDate>Thu, 15 Dec 2022 09:58:56 GMT</pubDate>
            <atom:updated>2022-12-15T09:58:56.855Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Before the project — </em>After last week’s chapter about things to do while you are coding, this week we’re back into things to do around the coding bits.</p><blockquote><em>The mistake new developers make often it to take this statement of need and implement a solution for it.</em></blockquote><blockquote><em>In our experience, this initial statement of need is not an absolute requirement. The client may not realise this but it is really an </em><strong><em>invitation to explore</em></strong></blockquote><p>Love this ^^. I think we are a bit patchy in how much we have internalised this. It is an issue I see fairly frequently. There are lots of techniques to open up a discussion but my favourite is just to ask “why?”.</p><blockquote><em>Your job is to help the client understand the consequences of their stated requirements</em></blockquote><p>Preach!</p><p><strong>What times can you think of where a more curious and flexible approach to “requirements” would have resulted in getting to the final implemented solution quicker?</strong></p><blockquote><em>May I sit with you for a week while you do your job?</em></blockquote><p>Yes! At (now defunct) energy company bulb, all software engineers also did sporadic shifts as Energy Specialists — the people who answered support requests — so that they could understand the customer needs, and the needs of the people they were building the internal systems for. Some engineers really didn’t enjoy this work but it certainly raised the understanding of the problems the team was trying to fix.</p><p><strong>Is there anyone we should be trying to sit with while they do their jobs? Have you ever tried this before? How was it?</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=32e5dbcef190" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Pragmatic book club chapter 7]]></title>
            <link>https://medium.com/@alice.bartlett/pragmatic-book-club-chapter-7-5e8267fa26d6?source=rss-5872a7f3d90a------2</link>
            <guid isPermaLink="false">https://medium.com/p/5e8267fa26d6</guid>
            <category><![CDATA[pragmatic-programmer]]></category>
            <category><![CDATA[book-club]]></category>
            <category><![CDATA[eningeering-book-club]]></category>
            <category><![CDATA[pragmatic-book-club]]></category>
            <dc:creator><![CDATA[Alice Bartlett]]></dc:creator>
            <pubDate>Thu, 15 Dec 2022 09:46:42 GMT</pubDate>
            <atom:updated>2022-12-15T09:46:42.119Z</atom:updated>
            <content:encoded><![CDATA[<p>Chapter 7, <em>while you are coding.</em></p><p>I don’t remember much about this chapter and I have no notes!</p><p>The main area for discussion in the first half was around refactoring because it’s a battle ground between our desire to ship things and our desire to built perfect things.</p><p>The metaphor about gardening as opposed to construction when thinking about code felt apt but I do wonder if perhaps there is no metaphor needed. Codebases, like gardens, like everything, tends towards entropy.</p><p>OK sorry, that’s literally all i’ve got. I think I was actually off sick for the second of our chapter 7 sessions, so if anyone else wants to fill in the blanks for me here <em>please do.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5e8267fa26d6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Pragmatic Book Club: Chapter 6]]></title>
            <link>https://medium.com/@alice.bartlett/pragmatic-book-club-chapter-6-b7de05d4b5f2?source=rss-5872a7f3d90a------2</link>
            <guid isPermaLink="false">https://medium.com/p/b7de05d4b5f2</guid>
            <category><![CDATA[engineering-book-club]]></category>
            <category><![CDATA[book-club]]></category>
            <category><![CDATA[pragmatic-book-club]]></category>
            <dc:creator><![CDATA[Alice Bartlett]]></dc:creator>
            <pubDate>Mon, 12 Dec 2022 14:06:36 GMT</pubDate>
            <atom:updated>2022-12-12T14:06:36.140Z</atom:updated>
            <content:encoded><![CDATA[<p>Sometime around October I had to take a break from leading the book club because my time got so extremely constrained that I could no longer squeeze it out. So from there the notes are a bit rougher and, as you will have noticed, greatly delayed. Nevertheless the book club kept going, and various people stepped up in my absence.</p><p>Let’s talk about chapter 6, Concurrency.</p><ul><li><strong>Mutexes in JavaScript, how would they work, how could they work</strong></li><li><strong>Where do we use concurrency?</strong></li><li><strong>Where do we use parallelism ?</strong></li><li>We talked a lot about the event loop this week as it os how concurrency is dealt with in JavaScript. <a href="https://www.youtube.com/watch?v=8aGhZQkoFbQ">Someone suggested this talk by Philip Roberts</a> as a good introduction.</li><li><a href="http://https//freecontent.manning.com/the-value-of-concurrency-in-tests">Https://freecontent.manning.com/the-value-of-concurrency-in-tests</a></li><li><a href="http://frontendmasters.com/courses/javascript-hard-parts-v2">Frontendmasters.com/courses/javascript-hard-parts-v2</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b7de05d4b5f2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Pragmatic Book Club: Chapter 5]]></title>
            <link>https://medium.com/@alice.bartlett/pragmatic-book-club-chapter-5-f5a0486951bb?source=rss-5872a7f3d90a------2</link>
            <guid isPermaLink="false">https://medium.com/p/f5a0486951bb</guid>
            <category><![CDATA[the-pragmatic-programmer]]></category>
            <category><![CDATA[book-club]]></category>
            <category><![CDATA[engineering-book-club]]></category>
            <dc:creator><![CDATA[Alice Bartlett]]></dc:creator>
            <pubDate>Fri, 07 Oct 2022 15:25:01 GMT</pubDate>
            <atom:updated>2022-10-07T15:25:01.282Z</atom:updated>
            <content:encoded><![CDATA[<p>Chapter 5 — bend, or break. We’ve hit the much more practical programming advice, although perhaps the advice is not always easily applicable to Node.js development. Attendance at our book club continues to be robust, usually at least 12 people, and it’s been a real pleasure exploring these ideas and how they apply or don’t to our work and our workplace.</p><p>We split this chapter over three weeks, and confusingly I have no notes what-so-ever for the first week. Luckily <a href="https://rowanmanning.com/">Rowan Manning</a> has shared his which are what follows:</p><h4><strong>Topic 28: Decoupling</strong></h4><ul><li>Subclassing isn’t always avoidable, depending on the language you’re working in. E.g. in JavaScript, extending Error (and coupling yourself to that interface) is pretty essential</li><li><em>“Developers who are afraid to change code because they aren’t sure what might be affected”</em> — <strong><em>is this fear familiar?</em></strong></li><li>These are some very in-depth examples. <strong><em>Did you follow the logic for the changes made in the Train Wrecks section?</em></strong></li><li><strong><em>What are your thoughts on “Don’t Chain Method Calls”?</em></strong> Again, always applicable? How often do you encounter JavaScript interfaces which encourage chaining?</li><li>Globals are littered all over our codebase, I bang my head against this a lot and it causes a lot of weird and difficult-to-debug issues. <strong><em>Do you have examples of places where globals are unavoidable? Are there ways we could make these things easier to debug?</em></strong></li></ul><h4><strong>Topic 29: Juggling the Real World</strong></h4><ul><li>Finite state machines! <strong><em>Who’s written an FSM or worked with an existing one? Do you have examples of how this has been useful at the FT?</em></strong> This is probably the most code I’ve read as part of this book so far, it seems quite in-depth.</li><li>The Observer Pattern is used pretty extensively in some of the core event-based Node.js modules as well as across the DOM on the client side. <strong><em>Aside from standard libraries in Node.js/browser, are you using the observer and publish/subscribe patterns anywhere in your code?</em></strong></li><li>JavaScript examples in Reactive Programming, Streams, and Events!?</li><li>Useful further reading on some of these patterns is Addy Osmani’s <a href="https://www.patterns.dev/posts/classic-design-patterns/">Learning JavaScript Design Patterns</a> (free)</li></ul><p>Onto my own notes now:</p><h4><strong>Topic 30: Transforming Programming</strong></h4><ul><li><a href="https://github.com/tc39/proposal-pipeline-operator">Pipeline operator appearing in JavaScript</a> — nice! Love that for us.</li><li>I spent some time working through this topic with some data I needed to transform and it was very enjoyable to play around with the idea in real life.</li></ul><h4><strong>Topic 31: Inheritance Tax</strong></h4><ul><li>Oh my god I never realised there were two originators of “inheritance” and now I understand why I find the Ruby/JavaScript kind of inheritance difficult to grok (because I wrote and understood inheritance through Java)</li><li>further reading: <a href="https://hackernoon.com/implementing-interfaces-in-javascript-with-implement-js-8746838f8caa">Implementing interfaces in JavaScript with Implement.js | HackerNoon</a> — As usual there is always some nerd who has taken things too far.</li><li>I used to find interfaces in Java very pointless, but then this book noted it means you can treat a bunch of objects the same, eg call .print() on them if they all implement the printable interface and I got it.</li><li>Another reason to like TypeScript.</li><li><strong><em>Are there any examples of us using interfaces and delegation across Customer Products?</em></strong></li><li><strong><em>Does anyone have a good set of patterns or a library which bring mixins to JavaScript?</em></strong></li><li><a href="https://www.patterns.dev/posts/mixin-pattern/">Mixin Pattern</a> on Patterns.dev is useful!</li></ul><h4><strong>Topic 32: Configuration</strong></h4><ul><li>We’re mostly OK at managing config at the FT.</li><li>We use Vault.</li><li>I’m not sure having runtime config changes (which would allow for zero downtime) is ever going to be important enough for the FT to prioritise what this chapter is suggesting.</li><li>Someone in our book club did make an allegation about Monzo that they do this.</li><li>One big issue with Vault is that there is no history to check when a key changed, which would be really useful!</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f5a0486951bb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Pragmatic Book Club: Chapter 4]]></title>
            <link>https://medium.com/@alice.bartlett/pragmatic-book-club-chapter-4-97304a2abdd1?source=rss-5872a7f3d90a------2</link>
            <guid isPermaLink="false">https://medium.com/p/97304a2abdd1</guid>
            <category><![CDATA[pragmatic-programmer]]></category>
            <category><![CDATA[engineering-book-club]]></category>
            <dc:creator><![CDATA[Alice Bartlett]]></dc:creator>
            <pubDate>Thu, 15 Sep 2022 10:23:34 GMT</pubDate>
            <atom:updated>2022-09-15T10:23:34.016Z</atom:updated>
            <content:encoded><![CDATA[<p>Chapter four, pragmatic paranoia. Now we’re getting into some more abstract and academic topics. Things we could think about introducing into our own codebases, even.</p><p>Section 23: Design by contract</p><ul><li>A completely unnecessary quote from the problematic Woody Allen. Great.</li><li><strong>Has anyone ever written clojure or elixir? Can you share a bit about how contracts form part of the language?</strong></li><li><strong>What would it take for us to introduce design by contract to Customer Products?</strong></li><li><strong>How do engineers at the FT reach a consensus on anything?</strong></li><li><strong>Would we need to change all of our existing code?</strong></li><li><strong>Would it be worth the effort?</strong></li><li><strong>Type is a form of c</strong></li><li><strong>[From the book] If DBC is so powerful, why isn’t it more widely used?</strong></li></ul><p>Section 24: Dead programs tell no lies</p><ul><li><strong>Is this mantra something you consider when writing code or reviewing other people’s?</strong></li><li><strong>Do you agree or disagree that with what the authors are saying about catching/re-raising exceptions on page 113?</strong></li><li><strong>The authors only give the reasons why not re-raising is better, what are the reasons you might want to catch and re-raise?</strong></li></ul><p>Section 25: Assertive programming</p><ul><li><strong>Do we use console.assert()?</strong></li><li><strong>When I read around this topic it seems like in a lot of places people are missing what is pointed out by the book <em>assertive programming should not be used to validate user input.</em></strong></li><li><strong>Why should asserts not be used for handling user input?</strong> Because the program shouldn’t terminate when a user inputs something incorrectly, as they will do often(?)</li></ul><p>Section 26: Balancing Resources</p><ul><li>This topic was pretty interesting to me, but it divided the book group. Some people felt it was not relevant to their day-to-day work. We predominantly write Node, and we use a lot of libraries. So the kinds of resource allocation issues this section talks about are often abstracted away and dealt with in those libraries.</li><li><a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Memory_Management">Good MDN article about memory</a></li><li>Good Katie Fenn <a href="https://www.youtube.com/watch?v=espDYUPBYJo">talk about garbage collection in Node</a></li><li><a href="https://technology.blog.gov.uk/2015/06/09/major-performance-issue-with-mustache-and-partials/">Blog post</a> from me from 2015 about a CPU usage bug I encountered and fixed in a mustache gem (Just to demonstrate that, rarely, we do encounter resource issues, even when writing front end code…)</li><li><strong>Anybody got any fun horror stories about resource allocation going wrong?</strong></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=97304a2abdd1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Pragmatic Book Club: Chapter 3]]></title>
            <link>https://medium.com/@alice.bartlett/pragmatic-book-club-chapter-3-c4b574d8b1b7?source=rss-5872a7f3d90a------2</link>
            <guid isPermaLink="false">https://medium.com/p/c4b574d8b1b7</guid>
            <dc:creator><![CDATA[Alice Bartlett]]></dc:creator>
            <pubDate>Thu, 01 Sep 2022 09:38:05 GMT</pubDate>
            <atom:updated>2022-09-01T09:38:38.876Z</atom:updated>
            <content:encoded><![CDATA[<p>I thought this was a pretty unchallenging chapter. Thanks in part to the success of this book, the sections (on the importance of plain text, the shell, fluency in the text editor, version control, debugging, text manipulation and engineering day books) went down very easily because these behaviours are all so deeply part of our working practices.</p><p>One theme that came up in our discussions a lot was how all of these techniques are very personal to the individual. This meant there was a lot of scope for discussions around favourite productivity hacks but nothing where we all agreed something was “essential” to being a great software engineer.</p><h3>On with the questions</h3><p>I didn’t come up with questions for every section as some of it was so uncontroversial I didn’t think there was anything interesting to discuss.</p><h3><strong>Editor fluency</strong></h3><p><strong>How many of these can you do?</strong></p><ul><li><em>When editing text, move and make selections by character, word, line, paragraph</em></li><li><em>When editing code, move by various syntactic units (matching delimiters, functions, modules…)</em></li><li><em>Reindent code following changes</em></li><li><em>Comment and uncomment using a single command</em></li><li><em>Undo and redo changes</em></li><li><em>Split the editor window into multiple panels and move between them</em></li><li><em>Navigate to a particular line number</em></li><li><em>Sort selected lines</em></li><li><em>Search for both strings and regular expressions</em></li><li><em>Temporarily create multiple cursors based on a selection or a pattern match and edit the text in parallel</em></li><li><em>Display compilation errors in the current project</em></li><li><em>Run the current project’s tests</em></li></ul><p><strong>How are we at these? Anybody really good (I am bad -sadblob) ? I feel like there must be an online game somewhere where you can test yourself on these types of skills.</strong></p><p><strong>Does anyone fancy “losing their mouse/trackpad for a week and going keyboard only”?</strong></p><h3><strong>Shell games</strong></h3><p><strong>Who is a shell wizard? Share your favourite shell commands and combos in the comments.</strong></p><h3><strong>Debugging!</strong></h3><p>Another thing I think we can all pat ourselves on the back about is how blame-free our engineering culture is at the FT. I reckon that starts with our approach to dealing with big outages, where there is a “blameless post mortem”, and <a href="https://www.etsy.com/uk/codeascraft/blameless-postmortems">idea I first heard about from Etsy</a>.</p><h3>Text manipulation</h3><blockquote><em>using [languages like ruby, python] you can quickly hack up utilities and prototype ideas — jobs that may take five or ten times as long in conventional languages</em></blockquote><p><strong>What features of a language make it “conventional” in the author’s definition do we think?</strong></p><p>Further watching: <a href="https://www.youtube.com/watch?v=VUhlNx_-wYk">Tom Stuart gave a good talk in 2011 about Ruby</a> which contains a nice framing of what language features are important to him and why he loves Ruby so much. I always share this with people who are puzzling out the differences between languages.</p><p>Like a lot of this chapter, the section on engineering daybooks was interesting and led to interesting discussions about what works for individuals</p><h3>Engineering day books</h3><p>Humble brag: I have had kept an engineering day book for the last seven or so years.</p><p>Increasingly weird brag: I use a slightly more chill variation on <a href="https://bulletjournal.com/">bullet journaling</a> to keep things somewhat organised. I use the Leuchtturm1917 A5 with dotted pages and I only write in it in BLOCK CAPITALS using a uniball eye fine in black because I have found that ink never smudges.</p><p>This practise is incredibly valuable to me as it builds in a monthly reflection on all the things I have to do, and it means I always have a list of to-dos to turn to when I sit down.</p><p><strong>I noticed </strong><a href="https://twitter.com/adgad?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor"><strong>Arjun</strong></a><strong> mentioned using </strong><a href="https://obsidian.md/"><strong>Obsidian</strong></a><strong> recently, anybody tried it?</strong></p><p><strong>What do you do for managing to-do lists, what’s good/bad about your approach?</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c4b574d8b1b7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Pragmatic Book Club: Chapter 2]]></title>
            <link>https://medium.com/@alice.bartlett/pragmatic-book-club-chapter-2-3aea0282e53a?source=rss-5872a7f3d90a------2</link>
            <guid isPermaLink="false">https://medium.com/p/3aea0282e53a</guid>
            <category><![CDATA[pragmatic-book-club]]></category>
            <category><![CDATA[book-club]]></category>
            <category><![CDATA[engineering-book-club]]></category>
            <dc:creator><![CDATA[Alice Bartlett]]></dc:creator>
            <pubDate>Tue, 30 Aug 2022 14:41:46 GMT</pubDate>
            <atom:updated>2022-08-30T14:41:46.749Z</atom:updated>
            <content:encoded><![CDATA[<p>We split chapter 2: A pragmatic approach across two weeks in order to stick to our limit of one hour of reading and 45 minutes of discussion per week. I was away on holiday for these two weeks but my very thoughtful colleagues <a href="https://twitter.com/teachlearncode">Jennifer Shepherd</a> and <a href="https://rowanmanning.com/">Rowan Manning</a> ran the sessions and the questions here are from them.</p><p>Following some slightly off-key framing in the <a href="https://medium.com/@alice.bartlett/pragmatic-book-club-chapter-1-ccd20e904839">first chapter</a>, which covered the pragmatic philosophy, the team was excited to get into less controversial topics in Chapter 2, which covers software design principles.</p><h3>Chapter 2, topics 8–11</h3><p>Framing from Jennifer:</p><blockquote>I’ve really enjoyed getting into the coding part of this book — it reminds me of when I first started at Makers Academy in 2018 and had lots of enthusiasm (and naivety!) about how beautiful and tidy all my applications could be!</blockquote><h4>DRY — The Evils of Duplication</h4><p><strong><em>To what extent does this reflect your experience at the FT:</em></strong></p><blockquote><em>We spend a large part of our time in maintenance mode, reorganising and re-expressing the knowledge in our systems.</em></blockquote><blockquote><em>Maintenance is not a discrete activity, but a routine part of the entire development process.</em></blockquote><ul><li><strong><em>Can you think of places this happens in the </em></strong><a href="http://ft.com/"><strong><em>FT.com</em></strong></a><strong><em> codebase? How easy would it be to reduce this?</em></strong></li><li><strong><em>How often do you find yourself having to change the same thing in more than one place across FT systems?</em></strong></li><li><strong><em>To what extent do you feel our communication methods at the FT help to reduce duplication across teams / groups? Where do you think we can improve?</em></strong></li></ul><p>I loved reading and thinking about duplication in documentation. So often I see out-of-date documentation and spend (waste) time reconciling the docs with the code I’m reading. I love comments in code in places where tricky or unexpected things occur, but I think we can do better at avoiding conflicts between comments / code / docs.</p><ul><li><strong><em>Where do we do this? Do you have experience of using tools that auto-create documentation?</em></strong></li></ul><h4>Orthogonality</h4><p>Again, love decoupling. Self-sufficient components that can be reused and rewritten and reintegrated?? This is the motivation behind “<a href="https://medium.com/ft-product-technology/no-next-next-42c71541ebcc">no next Next</a>”, and I guess the Sugababes.</p><ul><li><strong><em>Do you avoid writing tests because what you’re testing is not sufficiently decoupled? </em></strong>(broken windows theory…)</li><li><strong><em>Have you been able to improve our codebase by decoupling when you’ve made a change?</em></strong></li><li><strong>Here’s a similar question directly from the book relating to bug fixes:</strong></li></ul><blockquote><em>When you make a change, does it fix everything, or do other problems mysteriously arise?</em></blockquote><h4>Reversibility</h4><blockquote><em>If you rely heavily on some fact, you can almost guarantee that it will change.</em></blockquote><ul><li><strong><em>Do you have any examples of this?</em> <em>Where have we benefitted from expecting change?</em></strong></li></ul><blockquote><em>You also need to think about maintaining flexibility in the areas of architecture, deployment, and vendor integration</em></blockquote><p>I’ll end on a reflection that all of this sounds ideal but it is a lot to think about at the same time, especially for those of us who haven’t got 20 years of experience. It reminded me of the value of having diverse teams with varying strengths and depths of experience in each of these areas. And how great it is to run things past our lovely colleagues so that we can find our current blind spots!</p><blockquote><em>If you use the principle of orthogonality, combined closely with the DRY principle, you’ll find that the systems you develop are more flexible, more understandable, and easier to debug, test, and maintain.</em></blockquote><p><strong><em>[Bonus question from Rowan] Interested to know generally, with reversibility how much do you think this conflicts with the idea of premature optimisation? What is the right level of preparedness for change?</em></strong></p><h3>Chapter 2, topics 12–15</h3><p>These prompts are from Rowan Manning:</p><p>I generally found myself taking fewer notes on these topics, but can’t decide whether that’s because I know them or just find them less interesting than <a href="https://financialtimes.atlassian.net/l/cp/A8oULZwp">topics 8–11</a>. Possible questions to raise in the book club are <strong><em>bold-italic</em></strong>.</p><h4><strong>Tracer Bullets</strong></h4><p>I’ve never called it tracer code but this but working on a single vertical slice of the codebase makes sense to test that all the layers can interface with each other checks out.</p><ul><li><strong><em>Is this something you find you’re able to do at the FT?</em></strong></li></ul><h4><strong>Prototypes and Post-it Notes</strong></h4><p>“Make sure everyone understands that you are writing disposable code”.</p><ul><li><strong><em>How have you achieved this in the past? How successful was it? Do we have any prototypes in production?</em></strong></li></ul><h4><strong>Domain Languages</strong></h4><p>I did find this topic quite interesting, it got me thinking about whether there are any areas we could write our own domain languages to simplify parts of our estate. Is there something here in relation to helping other teams integrate with <a href="http://ft.com/">FT.com</a>? E.g. <a href="https://api.slack.com/block-kit/building">Slack’s Block Kit</a> is a domain-specific language for defining the UI and UI interactions in their app, and it’s incredibly powerful</p><ul><li><strong><em>Do you use any Domain Languages in your day-to-day work at the FT? Do they confer the benefits suggested in this topic?</em></strong></li></ul><h4><strong>Estimating</strong></h4><p>Interesting note on whether someone’s looking for high accuracy or ballpark estimates. Giving them a ballpark when they’re expecting high accuracy is a recipe for disappointment</p><p>I found this topic a little dry and the way we work [in my team] doesn’t result in a lot of time-based estimation lately. I may start tracking my own estimates anyway, even if they’re more personal targets than anything else.</p><ul><li><strong><em>What methods do you use for estimating in your teams? Are they accurate, or are they at least getting more accurate over time?</em></strong></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3aea0282e53a" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>