Better ROI from Software Development

In episode 150, I reintroduced this series with a new pitch. It was my way of taking what I've learnt over the last three years, the last 150 episodes, and almost 33 hours of content and updating the why the podcast.  Over the coming episodes, I'll take a deeper dive into the themes of the pitch and why they made the cut. Over the last few episodes, I've looked at the business side of the pit...

In episode 150, I reintroduced this series with a new pitch. It was my way of taking what I've learnt over the last three years, the last 150 episodes, and almost 33 hours of content and updating the why the podcast.  Over the coming episodes, I'll take a deeper dive into the themes of the pitch and why they made the cut.  In this episode, I follow on from last weeks introduction of chan...

In episode 150, I reintroduced this series with a new pitch. It was my way of taking what I've learnt over the last three years, the last 150 episodes, and almost 33 hours of content and updating the why the podcast.  Over the coming episodes, I'll take a deeper dive into the themes of the pitch and why they made the cut. In this episode, I wanted to talk about why I led with "Welcome to the...

In episode 150, I reintroduced this series with a new pitch. It was my way of taking what I've learnt over the last three years, the last 150 episodes, and almost 33 hours of content and updating the why the podcast.  Over the coming episodes, I'll take a deeper dive into the themes of the pitch and why they made the cut. If you listen back to the pitch, you will notice that it is almost half...

On the 23rd September, the UK Chancellor announces a series of change during a "mini-budget". The mini-budget, and its contents, have been the subject of much debate ever since. What might have been missed by many people where the changes to the IR35 off-payroll rules - which, as I discuss in this episode, could have material impact on both the contractor AND permanent recruitment markets Note: Si...

Welcome to the 150th episode of the podcast. In this episode, I take a moment of introspection to revisit the "pitch" for this series. ----- Find this episodes show notes at: https://red-folder.com/podcasts/150 Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

Over the last few episodes, I've focused on legacy software - what it is, how it occurs, and various strategies to deal with it. Alongside that legacy software is the legacy data - which is arguably more important than the data. In last week's episode, I talked about why thinking about that legacy data is so important. In this week's, I will provide advice for dealing with it. ----- Find this epis...

Over the last few episodes, I've focused on legacy software - what it is, how it occurs, and various strategies to deal with it. Alongside that legacy software is the legacy data - which is arguably more important than the data. In this episode, I want to talk about why thinking about that legacy data is so important ----- Find this episodes show notes at: https://red-folder.com/podcasts/148 Have...

This is part of a new mini-series looking at Legacy software - the term "legacy" is often seen as a positive - yet within computing it is a negative term generally uses to indicate the need to replace hardware or software. A few weeks ago, I introduced three methods to address legacy software: Evolution - continual improvement to the existing system to bring it out of its "legacy" state Revolution...

This is part of a new mini-series looking at Legacy software - the term "legacy" is often seen as a positive - yet within computing it is a negative term generally uses to indicate the need to replace hardware or software.  Two weeks ago, I introduced three methods to address legacy software:  Evolution - continual improvement to the existing system to bring it out of its "legacy" state&...

This is part of a new mini-series looking at Legacy software - the term "legacy" is often seen as a positive - yet within computing it is a negative term generally uses to indicate the need to replace hardware or software. In last week's episode, I introduced three methods to address legacy software: Evolution - continual improvement to the existing system to bring it out of its "legacy" state Rev...

This is part of a new mini-series looking at Legacy software - the term "legacy" is often seen as a positive - yet within computing it is a negative term generally uses to indicate the need to replace hardware or software. In this episode, I'll introduce three methods to address legacy software: Evolution - continual improvement to the existing system to bring it out of its "legacy" state Revoluti...

This is part of a new mini-series looking at Legacy software - the term "legacy" is often seen a positive - yet within computing it is a negative term generally uses to indicate the need to replace hardware or software. In this episode, I'll describe a simply risk matrix that can be used to monitor and highlight how legacy your software products are. ----- Find this episodes show notes at: https:/...

This is part of a new mini-series looking at Legacy software - the term "legacy" is often seen a positive - yet within computing it is a negative term generally uses to indicate the need to replace hardware or software. In this episode, I'll talk about some of the causes behind how our software can become "legacy". ----- Find this episodes show notes at: https://red-folder.com/podcasts/142 Have an...

This is part of a new mini-series looking at Legacy software - the term "legacy" is often seen a positive - yet within computing it is a negative term generally uses to indicate the need to replace hardware or software. In this episode, I'll talk about the impact of Legacy software and why the software industry invests so much effort into addressing. ----- Find this episodes show notes at: https:/...

This is the start of a new mini-series looking at Legacy software. The term "legacy" is often seen as positive - yet within computing it is a negative term generally uses to indicate the need to replace hardware or software. In this episode, I'll give you an introduction to Legacy software. ----- Find this episodes show notes at: https://red-folder.com/podcasts/140 Have an idea for an episode topi...

I've talked many times about the productivity benefits from automation. In this episode, I talk about the higher value benefits we get from automation - something you could describe as a side-effect. Automation gives us productivity - but not just to do more, but to do better.  Automation gives us the opportunity to elevate the work carried out by our teams - ultimately leading to better, che...

I've talked many times about the productivity benefits from automation. In this episode, I talk about the knowledge sharing benefits we get from automation - something you could describe as a side-effect. I discuss how, to be effective, any new software developer needs to learn not just the technical tools and practices, but also the domain - the environment in which the software will operate. I t...

I've talked many times about the productivity benefits from automation. In this episode, I talk about the auditability benefits we get from automation - something you could describe as a side-effect. I discuss: Why having audit data is helpful to our organisations How automation can help to provide that audit data How automation can remove a whole class of questions over manual access to productio...

I've talked many times about the productivity benefits from automation. In this episode, I talk about the security benefits we get from automation - something you could describe as a side-effect. I discuss: Reduced access Reduced manual interpretation Logs Controllable environments Automated security tools Signed software ----- Find this episodes show notes at: https://red-folder.com/podcasts/136...

In this episode I introduce Infrastructure-as-Code - a way of defining your Operation's infrastructure as code - an example of DevOps in practice with our Ops teams learning from our Dev teams. Why you may be interested in this episode: For an explanation of Infrastructure-as-Code The advantages of using it And some of the common excuses for not using it - and how to address them ----- Find this e...

In this episode I want to continue the talk about the team structures discussed on https://web.devopstopologies.com/ - with a focus this week on the topologies are shown to work. The devopstopologies.com website is based on the work by Matthew Skelton & Manuel Pais. I introduced Matthew and Manual as authors of the Team Topologies book in the last episode.  The work is a pre-cursor to the...

In this episode I want to talk about the team structures discussed on https://web.devopstopologies.com/ - with a focus this week on the anti-types. The devopstopologies.com website is based on the work by Matthew Skelton & Manuel Pais. I introduced Matthew and Manual as authors of the Team Topologies book in the last episode.  The work is a pre-cursor to the Team Topologies book - and wor...

In the last episode, I introduced "Conway's Law" - an observation of how our organisational structures influence our software structures. In this episode, I want to talk about how we can utilise this law when we want to improve problems in our software structures - commonly referred to as the "Inverse Conway Maneuver". Why you might be interested in this episode: A recap of Conway's Law and the ne...

In this episode, I introduce Conway's Law, which talks about how our software structures will reflect the structures of the organisations that create them. Why you might be Interested in this episode: Why our organisational structures affect software structure The history of "Conway's Law" The negatives that the Law can help us highlight And why the adoption of Microservices and small Cross Functi...