Legacy and tech debt are a fact of life in all software. So how can we identify the major causes and try to limit them… Read More »How Does Legacy and Tech Debt appear?

Why do we love to build new code when we have plenty of good software that already works? Is the platform language or framework legacy?… Read More »Legacy Code: Sunk Cost or Opportunity?

It’s a hard subject and one that I’ve debated with quite a few people. This episode is an exploration of a few themes and perhaps can offer some insights or perhaps is still a work in progress. I certainly have a few more avenues to explore around where the application stops and the CD implementation begins – plus should you design your CD implementation with that in mind.

What is legacy? What does it have to do with building new software? Why does it annoy us as software developers? Why does it worry… Read More »Is Legacy Scary? Or Is Building A New Software Product Scarier?

Tools and techniques are often fighting against what it means to be a software developer and provide little real value to the business either. It’s time to reevaluate. It’s time to take a new approach to how tools and techniques are applied in the industry when it comes to software delivery.

I talk to Tom Kennes, sustainable cloud consultant and ambassador for the Sustainable Digital Infrastructure Alliance (SDIA). We discuss how IT and software delivery can… Read More »Making Software More Sustainable with Tom Kennes

When was the last time you did a Minimal Viable Product that was actually minimal? How often do we get it right and truly focus… Read More »Putting the Product back in the MVP

In this episode we explore the way that technology, tools and architecture can affect the product that you are building. As engineers do we need to think more about product side? As product marketers what can we do to understand how the technology choice informs or limits our product possibilities? How do we deliver software in an open source project vs how do we deliver software in a corporate banking environment? What are the constraints that we need to be aware of in our decisions and how the customer need informs that. How we need to enjoy what we’re building – and make sure that we continue to enjoy building it as an individual, a team or as a company.

The same rules apply whether you’re a startup, a scale-up, a corporate, an individual, an open source project contributor. You’re part of your own support problem.

This time I discuss what it’s like to be a coder who wants to have it all – the good times and the bad times – but wants to limit the bad times to working hours only. I hope you enjoy it as much as I made recording it.