<?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 Ben Steele on Medium]]></title>
        <description><![CDATA[Stories by Ben Steele on Medium]]></description>
        <link>https://medium.com/@belfastnerd?source=rss-167e3e35b3bb------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*YadJ-qoFKCuiIuOFQRiqkQ.jpeg</url>
            <title>Stories by Ben Steele on Medium</title>
            <link>https://medium.com/@belfastnerd?source=rss-167e3e35b3bb------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 08:14:45 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@belfastnerd/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[Engineering Excellence… Introducing Sustainable Process Change.]]></title>
            <link>https://belfastnerd.medium.com/engineering-excellence-introducing-sustainable-process-change-276b2388af1d?source=rss-167e3e35b3bb------2</link>
            <guid isPermaLink="false">https://medium.com/p/276b2388af1d</guid>
            <dc:creator><![CDATA[Ben Steele]]></dc:creator>
            <pubDate>Sun, 21 Nov 2021 21:31:15 GMT</pubDate>
            <atom:updated>2021-11-22T08:09:02.595Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/271/1*Dy1xXyFE2hgnA5k76L7AFg.jpeg" /></figure><h3>Background</h3><p>My mentor always tells me, “play the long game&quot; and he is spot on. <br>I think of change needing to be regulated and fed into teams at a sustainable pace, especially if you work in a large program with lots of WIP (another article in the making here).</p><p>So when we started focusing in on engineering metrics around a monolithic workload. You start asking why are stage gates not enabled if there is the capability in your pipeline to production?</p><p>You could find a multitude of reasons: “It will slow teams down&quot;, “We will hold up the next release&quot;, etc.</p><p>There is a fallacy here as you start to rely more and more upon traditional QA talent and devalue them from doing high level exploratory testing by running repetitive test scripts. Well you get the picture… automation is your friend and you want to slow everything down, limit WIP and address underlying issues. At some point if you don’t address this you will hit a wall where CFR (change failure rate) or other factors stop you and force you to act.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/276/1*nXJLCAiLuhPtaQF9T_3B1g.jpeg" /></figure><h3>Sustainable Change Management</h3><p>You want to regulate change so you are supporting teams and not adding to the burden of WIP. Be it the introduction of the AWS well architected framework, accelerate metrics or stage gates. You want to break where you want to get to, into its most atomic form. You need to lay down a path and support your people to move past any inertia barriers.</p><p>Take a stage gate in a monolithic application, where do you start? It’s doesn’t matter what the technology stack is you need to look at the foundation. What is the testability of the application? Can teams write the tests you want to perform within the application? Culturally are teams prepared to deal with breaking builds or do they try and bypass them?</p><p>My team and I sat down and defined where we wanted to get to in our testing strategy and how we could tier gates which we called bronze, silver and gold. We looked at the minimum change we could implement in our stack it was Sonar blockers (our bronze gate). So we set a limit and got teams to work on reducing them over the coming sprint. We celebrated this change and looked at the next step. Limiting a minimum amount of code coverage on net new code (our silver gate).</p><h3>Ownership</h3><p>Now how do you bring this change about? I was inspired recently by Elon Musk and his comments around his engineering process and lesson learned including when receiving a requirement or constraint, it must come from “a name not a department. That person who’s putting forward the requirement or the restraint must take responsibility for that requirement. Otherwise you could have a requirement that an intern two years ago randomly came up with off the cuff and they’re not even at the company any more”, adding that this “has happened several times.”</p><p>Therefore you need to stick you name on what you expect teams to achieve and support them.</p><p>How do you let everyone know:</p><ul><li>Establish touch points with techleads and architecture in Dev forums.</li><li>Establish touch points with engineering management.</li><li>Don’t forget the business, having your product owners onboard is mission critical. This isn’t IT for ITs sake.</li></ul><h4>Run Comms wide and support teams with needs to self monitor themselves.<br><br>Good luck!</h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=276b2388af1d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Global Cloud-Native Platforms: Faster TTM, Reduce Operational Burden & Grow your Business!]]></title>
            <link>https://belfastnerd.medium.com/global-cloud-native-platforms-faster-ttm-reduce-operational-burden-grow-your-business-6ff836954e3f?source=rss-167e3e35b3bb------2</link>
            <guid isPermaLink="false">https://medium.com/p/6ff836954e3f</guid>
            <category><![CDATA[cloud-native]]></category>
            <category><![CDATA[wardley-mapping]]></category>
            <category><![CDATA[serverless-architecture]]></category>
            <category><![CDATA[serverless-first]]></category>
            <category><![CDATA[globalplatform]]></category>
            <dc:creator><![CDATA[Ben Steele]]></dc:creator>
            <pubDate>Thu, 25 Feb 2021 17:06:13 GMT</pubDate>
            <atom:updated>2021-02-25T22:49:09.785Z</atom:updated>
            <content:encoded><![CDATA[<p>I’d like to share my story of how we have scaled an idea from a meeting room in Boston all backed by a serverless-first mindset;</p><p>To a POT (Proof of Technology);</p><p>To a single country platform;</p><p>To a regional platform;</p><p>To a global platform backing a <strong>Multi</strong> <strong>Billion Dollar</strong> business across multiple LOB (Lines of Business)!</p><h4>Let me paint a picture:</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/791/1*VVBC5mdX3B0Mk8lt7kg31A.png" /></figure><h4>Technology Approach Explained</h4><ul><li>Cloud Native — Cloud-native is an approach to building and running applications that exploit the advantages of the cloud computing delivery model. Cloud-native is about how applications are created and deployed, not where.</li><li>IAC (Infrastructure As Code) — I’m privileged to work with a strong team of engineers who rubber-stamped their desire to drive towards an IAC approach, coupled with a multi-repo approach. This allows us to build once and deploy anywhere to any of our regional AWS accounts as all we need to do is supplement properties into our platform deployment properties build.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*1nSZxPTMoR9DDxmW.png" /><figcaption>Multi Tennant Design</figcaption></figure><ul><li>Multi Tenancy — Design at a container level, separated into separate ECS clusters and parameterised commodities (like functions, DynamoDB and other assets). This allows you to isolate environments within a VPC, we first realised we needed this to have a separate stack for evolving our architecture.</li><li>Serverless-first mindset — to coin the AWS CTO — <strong><em>“No server is easier to manage than no server.”</em></strong> — <a href="https://twitter.com/awsreinvent/status/652159288949866496?lang=en">Werner Vogel</a> . What does this mean? Well its it means you can focus on the core features you want to build, instead of worrying about managing and operating servers, databases, or storage systems. Ultimately once you have developed patterns and expertise in this space you can move really quickly. It doesn’t mean that you have no operational concerns, just that they are less and abstracted to a different level. Let me give you some of our working examples;</li></ul><ol><li>In my programme we needed a local logging stack in EMEA due to local compliance around logging. We assessed existing org SaaS offerings but the data residency remained a key blocker. So my team looked to experiment with a custom logging stack. We quickly spun up a suite of containers to provision the ELK (Elastic Logging) stack. We realised very quickly that we would need to manage this infrastructure, with maintaining EBS (cloud disk space) volumes, containers, clusters, etc. Our team wanted to prioritise other work, so we leveraged a stack using Cognito (to managed federated access), functions and ELK as a service to reduce TCO and operational burden — to me this is a serverless first approach.</li><li>Our team also provisioned clusters for running compute, we saw overhead with having to maintain the AMI’s backing clusters. So we added a feature into our templates to allow us to use AWS Fargate from managed EC2. This allowed us the flexibility to <strong>fallback</strong> where more granular compute options where needed as well as allowing a pathway for AWS to manage our compute reducing operational burden on our teams.</li></ol><h4>What is our platform?</h4><p>We are shipping <strong>Insurance as a Service</strong> holy based in the public cloud, using containerised products, AWS managed services, third party SaaS offerings and internally managed services backed by a buy over build design philosophy to support TTM.</p><h4>Evolutionary Architecture</h4><p>We took the time to decompose our stack based on Wardley Mapping (see <a href="https://learnwardleymapping.com/)">Simon Wardley)</a>. Simon Wardley talks about pushing something from an idea across the spectrum to a commodity (think SaaS and rental). Once we have defined our stack, moved it to IAC, we then worked on decomposition and multi-tenancy in parallel. An example of pushing commodity would be migrating from an internally managed Kafka cluster across to cloud native eventing technologies like SNS &amp; SQS or pushing from Oracle to AWS RDS Postgres to give you a small flavour of what we have done as we seek to push the platform towards a commodity.</p><h4>Global Design &amp; Time to Market</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/636/1*TPPuyrK-eUb83TRzyj1adQ.png" /><figcaption>Regional Instance Strategy</figcaption></figure><p>Our original build took us <strong>months </strong>to provision, we can now ship our platform in a <strong>week</strong> to a new region as we have pushed our core stack towards more of a commodity.</p><p>It is also critical to know if your value chain is working. Feedback loops are a mixture of <strong>daily best practices, automation, and tools</strong>. The last thing you want is for your users to be really excited about what you have done, and then be mad when it blows up all over the place.</p><p>We have constantly worked with senior stakeholder to demo our capabilities and how we evolve through live demo’s, videos and presentations.</p><h4>What is a north star metric and why does it matter?</h4><p>A north star metric is the key measure of success for the product team in a company. It defines the relationship between the customer problems that the product team is trying to solve and the revenue that the business aims to generate by doing so.</p><p>There are essentially 3 types of product games:</p><ol><li><strong>The Attention Game: </strong>How much of your customers’ time can you capture in your product.</li><li><strong>The Transaction Game: </strong>How many commercial transactions does your user make on your platform.</li><li><strong>The Productivity Game: </strong>How many high value digital tasks can your customer perform in your product.</li></ol><p>Working with stakeholders to derive a roadmap and goals through the NorthStar framework (<a href="https://info.amplitude.com/north-star-playbook">see Amplitude</a>) was a valuable process for bringing around cultural change and forming a global team as we all bought into a common purpose rallying around reducing operational expenditure through a serverless-first mind set; whilst focusing on new channels to increase NWP (net written premium) through standardised products. We also are lucky to have a very strong business whom have accelerated acquisition into our business model through opening new channels like the aggregator. The creation of this platform has stated a cultural revolution in our wider company as we look to drive reusable capabilities across the enterprise.</p><p>Now as we continue to scale our BOB across multiple LOB and new channels, we do need to continue to focus on decomposition, managing reusable products and looking to support access to third parties. More to follow as we continue this journey! The good news is having a cloud native platform means you have flexibility to scale workloads through code which is amazing when you think they we used to have to manually provision compute in a physical data centre.</p><p>You can follow me on: <a href="https://mobile.twitter.com/belfast_nerd">https://mobile.twitter.com/belfast_nerd</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6ff836954e3f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My Positive Tech Predictions for 2021!]]></title>
            <link>https://belfastnerd.medium.com/my-positive-tech-predictions-for-2021-97de024304b8?source=rss-167e3e35b3bb------2</link>
            <guid isPermaLink="false">https://medium.com/p/97de024304b8</guid>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[predictions]]></category>
            <category><![CDATA[future]]></category>
            <category><![CDATA[2021]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Ben Steele]]></dc:creator>
            <pubDate>Tue, 24 Nov 2020 22:14:21 GMT</pubDate>
            <atom:updated>2020-11-25T08:06:58.800Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*bM-P2FAyEOEE_zxqcwQJ7w.jpeg" /></figure><h3>1. Rise of a Public Cloud playing Green</h3><p>Never has it been so easy to provision workloads in the public cloud. It got me wondering, right now we use serverless and other times we run with dedicated compute that’s been provisioned.</p><p>Unless you are spending time scaling the later, you will have capacity which isn’t doing anything and burning energy (forget cash 😂).</p><p>What if your public cloud workload got an energy rating, like your fridge?!</p><p>Whilst I free type; it also makes me think this will inevitably play into a serverless first mindset where you only pay for what you use. The same would apply to energy. That’s not to say you would be ignorant of designing serverless workloads. For instance you still assign resources to a lambda, but then do you need to even call it? Could we see a shift to “green patterns” or green availability zones in the public cloud.</p><p>I live in the West of Ireland and right now AWS are buying wind turbine capacity to offset their data centre power usage. BUT this doesn’t necessarily directly power the data centres, but offsets it. Is this good enough? (Maybe ive gone down a rabbit hole here 🙂)</p><h3>2. Multi Cloud Swings and Roundabouts</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VTxtbBTuDs-XjSjOHkiDoA.jpeg" /></figure><p>I work in technology professional services; personally I would ask anyone adopting a multicloud strategy outside of a vendor product to justify where there business case is for multi cloud. BUT with the public cloud providers outside of AWS maturing I can see a pivot for this to open more.</p><h3>3. Drone delivery to your garden</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hHylqzFLhpSVw_dkn32CFQ.jpeg" /></figure><p>In the West of Ireland we are seeing drones now trialing delivery services in Oranmore, Galway. Once drone technology can move outside point to point deliveries, I think we will see a rapid rise in drones operating localised delivery services.</p><h3>4. Global talent pools</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/728/1*gbF3tXs-oSWDxh8e1zqPiA.jpeg" /></figure><p>I’m privileged to be working for a fortune 100 company that’s trying to go global. I also work with a team that’s distributed across Ireland and Poland.</p><p>I’ve been working remotely now for 5 years and I believe it doesn’t matter where in the world you are if you can get the job done. In a thriving market technology professionals, talent will start to look outside of the large technology centres and start to think about global talent.</p><h3>5. Evolution of remote working</h3><p>As companies dump their commercial footprints in 2021. I think we might see more structured options around remote working. If the new norm for technology working is asynchronous working patterns, might we see a new suite if tooling to support a market for these new ways of working?</p><p>Will business travel crash as a result of 2020? Which could surely a good thing for those of us with families. The days of the CEO landing in for the day and everyone having to be at their desks is surely over.</p><p>I mean who would have thought the office 2020 Christmas party would be remote!!!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=97de024304b8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Psychology of Focus: How Great Teams Find Their Way]]></title>
            <link>https://belfastnerd.medium.com/the-psychology-of-focus-how-great-teams-find-traction-amid-distraction-778228d222ff?source=rss-167e3e35b3bb------2</link>
            <guid isPermaLink="false">https://medium.com/p/778228d222ff</guid>
            <category><![CDATA[business-strategy]]></category>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[focus]]></category>
            <category><![CDATA[kpi]]></category>
            <category><![CDATA[northstar-framework]]></category>
            <dc:creator><![CDATA[Ben Steele]]></dc:creator>
            <pubDate>Fri, 20 Nov 2020 19:24:55 GMT</pubDate>
            <atom:updated>2020-11-20T21:53:35.819Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AhgGno8WPLCxYMB8VaEB8Q.jpeg" /></figure><p>The opposite of purpose is emptiness. Top business leaders have a dedicated focus that’s relentless.</p><p>One of the key elements to surviving difficult times is to remain ruthlessly focused on key objectives for your team.</p><p>I have the privilege of working with a small team of craftsmen; in a massive fortune 100 enterprise. One would think it’s hard for a team of 6 to make an impact, BUT you really can! So how do you breakout of JIRA and start to help author a better destination with your company executives? One really useful tool is the:</p><h3>Amplitudes North Star Framework</h3><p>It is a model for managing products by identifying a single, leading KPI/metric (the North Star Metric) that your company cares about. (See John Cutler and Amplitude who authored this)</p><p>It’s been utilized to great effect in other companies such as LinkedIn and Spotify.</p><p>In addition to the metric, the North Star Framework includes a set of key inputs that collectively act as factors that produce the metric. Product teams can directly influence these inputs with their day-to-day work. This is the magic sauce here, it’s about connecting teams with the business imperatives.</p><p>This combination of metric and inputs serves three critical purposes in any company:</p><ul><li>It helps prioritize and accelerate informed but decentralized decision-making.</li><li>It helps teams align and communicate.</li><li>It enables teams to focus on impact and sustainable, product-led growth.</li></ul><p>Put together, the metric and the inputs look like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*DeJhS99iLCqEDzrIFti57w.jpeg" /></figure><h3>How it helped us</h3><p>We were able to bridge communication gaps, it brought leadership together as we evolve out of a supporting role. Some of my colleagues like Michael O’Reilly have utilised this to great effect, so it’s not a fluke.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6l7fIh18Z67qshyJ8W0kbA.png" /></figure><p>Its allowed decision makers to all get their ideas out there. Then it allowed us to consolidate down on a common goals.</p><h3>Summary</h3><p>Teams that apply ruthless prioritization are more resilient through these turbulent times as they are driven to the mission.</p><p>Reading a tweet from Gregory Hope this week: “Even though a chain pulls into a direction, all links are equally important - one breaks, the chain breaks”.</p><p>Some teams in large enterprises are busy crafting excellent solutions that simply needed in isolation.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=778228d222ff" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Migrating to Blue/Green with AWS CodeDeploy]]></title>
            <link>https://belfastnerd.medium.com/migrating-to-codedeploy-with-aws-blue-green-465e3f8340e0?source=rss-167e3e35b3bb------2</link>
            <guid isPermaLink="false">https://medium.com/p/465e3f8340e0</guid>
            <category><![CDATA[cicd]]></category>
            <category><![CDATA[codedeploy]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[aws-testhook]]></category>
            <category><![CDATA[aws-codedeploy]]></category>
            <dc:creator><![CDATA[Ben Steele]]></dc:creator>
            <pubDate>Thu, 12 Nov 2020 19:27:46 GMT</pubDate>
            <atom:updated>2020-11-20T08:59:26.568Z</atom:updated>
            <content:encoded><![CDATA[<p>The purpose of this document isn’t a guide to standing up CodeDeploy, AWS have brilliant documents for this. I want to share the lows and highs to accelerate my key learnings from adding Blue/Green transforms to an existing stack.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*QLzGZGArSthY2OrouS4E-A.png" /><figcaption>Diagram of orchestration</figcaption></figure><h3>Why bother?</h3><p>The idea here is that your business has zero down time. It also creates a better development experience for teams, enabling them to safely ship their features.</p><h4>Jargon:</h4><p><strong>Deployment Configurations</strong>; AWS supports Canary, Linear or All-at-once cut over strategies. I opted for all-at-once which will shift 100% of the production traffic once my tests have passed.</p><p><strong>Deployment Types</strong> available are isolated where you configure a CodeDeploy Application or Assimilated into existing deployments. Here we examine the later option.</p><h3>General Design Constraints</h3><p>Compute platforms of <strong>lambda</strong> and <strong>ECS</strong> are supported.</p><p>Imports and exports are <strong>not</strong> exported, though exports seem to work.</p><p>A custom lookup on resources won’t work for some resources, like service level roles for running your task sets.</p><p>You can only specify a <strong>single</strong> ECS service as the deployment target.</p><p>We typically orchestrate a cluster and then have a separate template for a service, obviously if you embrace lambda you won’t have this burden as you not working with clusters, but nested stacks are not supported.</p><p>From a cost perspective you can create more clusters at 0 cost anyway. You will want to understand the path to production for releasing this.</p><p>For orchestrating across multiple stacks, you could potentially use hooks to do this although AWS don’t recommend this. We have versioned our lambdas for the rest of our workloads and then injected versions into an nginx proxy, but will cover that another time. I’m currently working on the testing this stack and I think there is good opportunity to bring in serverless testing frameworks which could run in parallel.</p><h3>Key Lessons</h3><p>Where is my deployment!? When you create a deploy for the first time, it won’t trigger a blue green deploy until a subsequent deployment.</p><p><strong>CFT Parameters</strong>; default CFT parameters will result in a failure on a subsequent deploy , note to self its bad practice IMO.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/468/1*QlXITX5x0AMbUXlpbwKtOw.png" /><figcaption>default params a no no</figcaption></figure><h4>BREAKING changes!?</h4><p>Redeployments with breaking changes … if theres one thing you take from this before you start its this:</p><p><strong>***You cannot include updates to multiple resources at once***.</strong></p><p>· <a href="https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-ecs-taskdefinition.html">AWS::ECS::TaskDefinition</a></p><p>· <a href="https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-ecs-taskset.html">AWS::ECS::TaskSet</a></p><p>Updates to the above resources with updates to other resources in the same stack WILL FAIL and no linter will tell you. If you need to update resources in the list above as well as other resources in the same stack, do one of the following scenarios (I recommend the first):</p><p>· Perform two separate stack update operations: one that includes only the updates to the above resources, and a separate stack update that includes changes to any other resources.</p><p>· Remove the Transform and Hook sections from your template and then perform the stack update. In this case, CloudFormation will not perform a green deployment.</p><p>Or else! Yes I did try it, because I don’t want to see this in production.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/468/1*rjtNbymNV20Smu4tM8RDFQ.png" /></figure><p><strong>Lambda imports;</strong> need to be hardcoded which is bad, AWS best practice is to use auto naming and I find it makes stacks easier to share as templates. Try intrinsic value lookups and ambiguous stack errors will follow.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/517/1*pmC3C2yYB6yOleU7a_Pfkw.png" /></figure><p><strong>Default timeouts</strong> are set at 1hr for CodeDeploy, so make sure you have a decent catch block for failed scenarios:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/390/1*kWy7qtutq3zixxD-qZDhyQ.png" /><figcaption>1hr timeout</figcaption></figure><h3>So why use it?</h3><p>Positives here, its forced our work into a shift toward automated testing for everything, which is obviously best practice. I’m hoping that I can quickly update this article and that AWS mature this offering.</p><p>All in all, I like it. You could code all this yourself, but I would rather that AWS reduces our operational burden here and allows us to focus on delivering business functionality.</p><p>It’s going to be easier for teams to ship feature changes.</p><p><strong>References:</strong></p><p><a href="https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/blue-green.html">https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/blue-green.html</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=465e3f8340e0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Metrics Matter...]]></title>
            <link>https://belfastnerd.medium.com/metrics-matter-ffb6b9af3e0?source=rss-167e3e35b3bb------2</link>
            <guid isPermaLink="false">https://medium.com/p/ffb6b9af3e0</guid>
            <dc:creator><![CDATA[Ben Steele]]></dc:creator>
            <pubDate>Tue, 31 Mar 2020 08:40:09 GMT</pubDate>
            <atom:updated>2020-04-03T22:01:40.816Z</atom:updated>
            <content:encoded><![CDATA[<h3>Metrics Matter... Testing Parallels between the Covid19 crisis and my experiences in Software Engineering.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2HD9uk4JcoUA4Hkyq6f5dQ.jpeg" /></figure><h4>Covid19 Vs A Software Quality Pandemic</h4><p>How the worlds governments have reacted to testing of Covid19 reminds me of certain execs in large enterprises. Some sponsor active leadership and look to empower their teams, destroy hierarchical reporting structures in a psychologically safe environment which Foster’s innovation from engineering teams, whilst other utter nonsense about herd immunity or in engineering that might be a status chart, whilst passing critical conversations over core engineering practices (TDD, BDD, Code Quality, etc).</p><p>I’m drawing a parallel here between the health care capacity to operate and that of a large engineering program. In order to thrive we need to have capacity and culture to focus on delivering customer centric solutions that are founded in innovation and quality.</p><p>What are folks on your programme discussing ???</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WzeLz6kJeMDHjUpWg9BTgA.jpeg" /></figure><p>When it comes to engineering excellence the good news is you don’t need to find perfection, you just need to level set as a programme where you want to get to, explain and discuss what your goals are and enable your talent to understand how you achieve it. Ideally with a dashboard that’s the trusted source of truth. Then keep iterating... easy right?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*eAnowjwKAl4ifIE3kbTcjg.jpeg" /></figure><blockquote>Exec… if we turn the quality gates on it will slow us down. Engineer… yes, we may have to go slow to go faster than if we leave them disabled.</blockquote><h4>How do you flatten the curve?</h4><p>It’s a cultural shift in getting everyone to understand why testing is important and what’s in it for them. Execs who invest in enabling cultural shifts in this space may have to explain why they are moving slow in order to go faster. But they will win the war. Though if you leave it too late you will end up with a lack of confidence in your main develop branch as you watch lead time plummet off a cliff.</p><h4>Creating the culture</h4><p>A culture of testing is based on the premise that no single tool, test, or person can guarantee quality. For quality to be a solid part of the company culture, everyone needs to support and contribute to it—from management and the business to developers, architects, and product managers.</p><p>As with any project, we will have some challenges to solve. When I first started this culture shift with my latest partner. I found that onboarding of teams, having time dedicated to proper team norms and test strategies are non negotiable. I always tell engineers, don’t worry how we write a test, how would you test this manually?</p><h4>Winning conversations with execs</h4><p>So how do you frame your conversations better with execs? With Data! Anyone ever heard of accelerate metrics which focus on high performance engineering?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dhwYcKwVXrCGQ_wfBPivAQ.jpeg" /></figure><blockquote>The moral of the story, borne out in the data, is this: improvements in software delivery are possible for every team and in every company, as long as leadership provides consistent support — including time, actions, and resources — demonstrating a true commitment to improvement, and as long as team members commit themselves to the work.</blockquote><p>Nicole Forgren, Jez Humble and Gene Kim coin four key metrics:</p><p><strong>Lead Time</strong>: the time it takes to go from a customer making a request to the request being fulfilled.</p><p><strong>Deployment Frequency</strong>: frequency as a proxy for batch size since it is easy to measure and typically has low variability. In other words, (desirable) smaller batches correlate with higher deployment frequency.</p><p><strong>Mean Time to Restore (MTTR)</strong>: as software failures are expected, it makes more sense to measure how quickly teams recover from failure than how often they happen.</p><p><strong>Change Fail Percentage</strong>: a proxy measure for quality throughout the process.</p><p>These KPI’s are powerful because they focus on global outcomes and capture many intangibles (such as “quality”) throughout the Software Development Lifecycle (SDLC). Accelerate proposes these KPIs, but does not offer a method of capturing them throughout the SDLC. This post suggests possible approaches and solutions for measuring these KPI’s.</p><p>Other engineering metrics such as code coverage, big, vulnerabilities, code duplication, etc are all great metrics and should be set as enabling constraints within any decent pipeline, but if you want to frame to an exec who doesn’t get these, they will understand lead time. Accelerate metrics help us frame to leaders engineering metrics which matter.</p><blockquote>Testing has never been more relevant in today’s market where it’s all about enabling business outcome and speed to market, here’s to my engineering peers who want to flatten the tech debt curve.</blockquote><p>Stay safe, avoid change approval boards and follow me on: @belfast_nerd</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ffb6b9af3e0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My Working From Home Guide, The New Norm?]]></title>
            <link>https://belfastnerd.medium.com/my-working-from-home-guide-the-new-norm-4241001387c?source=rss-167e3e35b3bb------2</link>
            <guid isPermaLink="false">https://medium.com/p/4241001387c</guid>
            <category><![CDATA[wfh]]></category>
            <category><![CDATA[remote-working]]></category>
            <category><![CDATA[working-from-home]]></category>
            <category><![CDATA[remote]]></category>
            <category><![CDATA[remote-work]]></category>
            <dc:creator><![CDATA[Ben Steele]]></dc:creator>
            <pubDate>Mon, 16 Mar 2020 11:37:36 GMT</pubDate>
            <atom:updated>2020-03-16T18:29:11.267Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*8zMEGZpR8jsFJ8AO8duPmw.png" /></figure><p>In 2015 I relocated to the West of Ireland to my wife’s home village in Moycullen, Connemara Galway. I approached my employer (a global digital organisation) six months prior to moving, expecting that I would end up leaving to seek alternative employment. I was lucky and pleasantly surprised that my employer offered me the opportunity to work into a new office in Dublin Ireland and explore working from home.</p><p><strong>Connect with your teams, people are social creatures, our talents mental wellbeing is paramount</strong></p><p>As the <a href="http://www.health.harvard.edu/newsletter_article/the-health-benefits-of-strong-relationships">Harvard Women’s Health Watch</a> reported, “Dozens of studies have shown that people who have satisfying relationships with family, friends and their community are happier, have fewer health problems, and live longer.”</p><p>In a <a href="https://academic.oup.com/aje/article-abstract/109/2/186/74197/SOCIAL-NETWORKS-HOST-RESISTANCE-AND-MORTALITY-A">study of 7,000 men and women</a> in Alameda County, Calif., begun in 1965, Lisa F. Berkman and S. Leonard Syme found that “people who were disconnected from others were roughly three times more likely to die during the nine-year study than people with strong social ties,” John Robbins recounted in his marvelous book on health and longevity, “Healthy at 100.”</p><p>This major difference in survival occurred regardless of people’s age, gender, health practices or physical health status. In fact, the researchers found that “those with close social ties and unhealthful lifestyles (such as smoking, obesity and lack of exercise) actually lived longer than those with poor social ties but more healthful living habits,” Mr. Robbins wrote. However, he quickly added, “Needless to say, people with both healthful lifestyles and close social ties lived the longest of all.”</p><p>With Covid19 now making the headlines, social anxiety is being exacerbated through digital platforms.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/499/1*cXPcR0pTUa-xjYnYqjDb6Q.png" /></figure><p><strong>“Remote First” for the win</strong></p><p>Remote first doesn’t mean that we have an employee or two who works in some obscure part of the country. Remote first is about making an immersive experience for the whole team.</p><ol><li>Video conferencing by default: sometimes you need to be brave and turn on your web cam to start this off if you are new to this environment. You will quickly find people stumbling to follow suit. Web camera help us increase our connectivity and I’d find it impossible to not do this in most meetings now.</li><li>Consider geographical distribution: are you working with colleagues in different locations, this is one thing. But different timezones means you need to consider everyones working day, there might only be a few hours of overlap in a working day. Inviting people to late night meetings without consideration of their location won’t go down well if it becomes the new norm.</li><li>Discuss ways of working: different people have different needs, most of our team likes to pair programme and it’s a great way to mentor and learn if done correctly. I think it’s fine if some people prefer not to partake in this, though the team then needs to figure out how they can reach out to them more, so they don’t become disconnected.</li><li>Be creative: I hit some VPN issues last week, it took my boss to point out that I can just turn the VPN off and still connect to Skype without having my bandwidth throttled. Explore new tools, there is a plethora of them out there.</li><li>Make a list: I make a list every day, I’m not sure what it is, but it feels good to tick things off a list. Sometime I even cheat adding something tiny that I already know is basically done.</li><li>Make sure you have a suitable space to work from… I’m sorry the kitchen table or couch doesn’t cut it and I’ve never done this. You need to be focused and disciplined to make this work. If you are lucky enough to have fibre, invest in fibre to the home, so no one can ever claim that you are being less productive by WFH.</li><li>Don’t put off meetings: cancelling meetings because you are going to be in the office next week generally isn’t a great idea. I always try to think, what value am I going to add here. In general, if you don’t think you will add value to a meeting, don’t go.</li></ol><p><strong>Life Balance is Important</strong></p><p>Try and keep to a routine, you may need to book a slot for lunch. I have at times found myself getting stuck to my mac. It takes more discipline to step away and take lunch or even better, why not exercise!?</p><p><strong>Summary</strong></p><p>You are only valuable to your employer if you are delivering value to their business. Make technology work for you. I’m really lucky to work with some of the top talent in my organisation and we are a remote first team. This means putting everyone on a level playing field.</p><p>With the outbreak of Covid19, employee’s are now falling into remote working without a proper setup. So we need to support our talent and we could change how we all work in the future.</p><p>Follow me on <a href="https://twitter.com/belfast_nerd">@belfast_nerd</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4241001387c" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>