127: Agile Practices in Legacy Code Mending with Michael Toppa
Agile has become the mainstream in software engineering, and agile principles should feel natural to legacy code menders.
Agile has become the mainstream in software engineering, and agile principles should feel natural to legacy code menders.
Imagine if you could refactor legacy code with a single CLI command? Well, you can, at least if you are working with PHP.
There is a lot of buzz around Kotlin, a new Java-based programming language that many think might eventually replace Java.
We all want our code to be stable and resilient to future challenges. But we need to strike the right balance between testing our systems and the cost of failure.
We all strive to write an ideal code - easily readable, functional, and clean. We use many tools to achieve this. However, we often forget why we need our code to be tidy.
Imagine if you could compare concepts side-by-side between a programming language you know and one you don't. Well, now you can!
Coders spend most of their time reading rather than writing code. Yet, when you look at the undergraduate programs, boot camps, and conferences, everything seems to be dedicated to code production.
Some of the biggest risks for cyber security frameworks come from employees meant to maintain them.
Agile is all about the speed of iteration and execution. One of the things that often gets neglected is the business impact of the code we are shipping.
We frequently discuss compassion, empathy, and kindness on this podcast. What we rarely focus on, however, is being kind and compassionate to ourselves. Today we talk with Clare Sudbery.