132: Software Security with Rob Dickinson
Software security has become one of the most important topics affecting the lives of millions of people.
Software security has become one of the most important topics affecting the lives of millions of people.
We design software within a particular context. When that context changes, so should the software. But change is often difficult.
If you try to fix broken things in JavaScript, you will probably break the Internet because the entire Internet expects those "mistakes" to be there.
Legacy becomes legacy only when the memory of how the system works is gone. This is where observability kicks in. Today we talk with Hunter Madison.
The world as we know it wouldn't exist without open-source software. We have learned to rely and depend on these free products that magically get maintained and updated by communities of volunteers.
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.
Legacy Code Rocks explores the world of modernizing existing software applications.
In this show, hosts M. Scott Ford and Ray Myers are out to change the way you think about legacy code.
If you're like a lot of people, when you hear the words "legacy code" it conjures up images of big mainframes and archaic punch card machines. While that's true — it only tells a small part of the story. The code you leave behind is your legacy, so let's make it a good one.