Operations | Monitoring | ITSM | DevOps | Cloud

In this article, I’ll provide a guide to Git for non-developers. So, if you are reading this as a full experienced Git user, you may disagree with some of my statements. Don’t bother reading on; we recognize you as the expert! If, on the other hand, you’re new to Git, this piece is for you.

At the end of 2021, we published a blog post about the Autumn budget in the UK, what it meant for IT teams in the NHS, and why data management should be prioritised. We looked specifically at four key areas for sharing, monitoring, protecting, and accessing data that we believe are crucial elements of the digital transformation journey. Digital transformation is part of the NHS Long Term Plan, a wide-ranging programme to upgrade technology and digitally-enabled care across the NHS.

This is the fifth part in the DevOps 101 series and it’s time to talk about automation. Before we get into it, I just want to recap what DevOps is. Microsoft’s Donovan Brown sums it up nicely in a single sentence: DevOps is the union of people, process, and products to enable continuous delivery of value to our end users. The important thing to remember here is the order in which he talks: people, process, and products. That’s the way DevOps works.

Interrupts are often seen as a problem that eats away at your team’s productivity, and gets in the way of shipping important things for your customers. It’s often consciously accrued from the tech debt we accept to ship features sooner. However when a team doesn’t have a good strategy for dealing with the consequences of those decisions, the pain is felt much more acutely and much sooner.

Cloud computing can bring many benefits to financial services companies such as increased speed and agility, easier innovation and scalability. It is no wonder then that cloud adoption is set to continue increasing with 54% of financial services companies expected to have more than half of their entire IT footprint in public clouds in the next five years. However, despite the benefits that this can bring for financial services, it also brings a new set of challenges for financial market stability.

Everyone in the software industry is in a race to become more agile. We all want to improve the performance of our software development lifecycle (SLDC). But how do you actually do that? If you want to improve your performance, first determine what KPI you’d like to improve. DORA metrics offer a good set of KPIs to track and improve. It started as a research by the DevOps Research and Assessment (DORA) and Google Cloud (which later acquired DORA), to understand what makes high performing teams.