Legacy Code Rocks

We seldomly dive deep into discussing any particular programming language on this show. However, today we are making an exception, and we talk with Chrissy LeMaire about PowerShell. Chrissy is a GitH…

We behave with the cloud as a subset of technology like a teen who just learned how to drive. We are at the point where capabilities have far exceeded the ability to comprehend consequences. We have …

Technical debt is a recurring theme of this show. We talk about it almost as often as it pops out in any legacy code! Today we go back to discussing technical debt with Jim Humelsine. Jim has been a …

Many legacy systems lack adequate test coverage. They might not have much coverage at all, or the existing tests might be inefficient or paint a wrong picture about the stability of the system. Enhan…

There has been a noticeable uptick in the adoption of public cloud providers. At the same time, the voices advocating for the abandonment of traditional data centers are getting louder. Keeping serve…

Common Lisp was written in the 80s as a kind of an amalgam of the existing Lisps at the time. To make sure the Common Lisp would stay relevant, it was made backward compatible so that existing legacy…

Software engineers perceive that technology advances in an orderly, linear fashion. This makes the novelties very attractive. However, the reality is that we tend to go through technology in cycles. …

For most teams, dependency freshness is a pain that is often ignored. “If it works –don’t change it” is the prevailing attitude, but as a lot of applications become web-focused, dependencies inevitab…

When developers talk about what they find exciting, they usually talk about new things. Very little content is about the actual job, about working in the existing system. When they do talk about lega…

We like to think that technology is our objective and neutral assistant, our faithful lieutenant constrained with science and armed with cold, hard data. But this is incorrect. Technology reflects th…

Many analytical models can help you to measure some aspects of the quality of your codebase. However, only a combination of these models can give you complete information about your code's integrity …

Ruby on Rails is a fast-moving community and it is not always easy to keep up with it. Given the efficiency of the framework, however, it is well worth trying. Today we talk to Robby Russell, creator…

Security is a big topic with many facets, and this is especially true for microservices. Microservices deployment has been around for some time, but security didn’t get much attention from developers…

In the last episode of 2020, we took a stroll through the little known corridors of coding history with Clive Thompson. Clive is a technology and science journalist for the New York Times Magazine, W…

Even before the COVID-19 pandemic changed the way we work and communicate, some people expected remote work to become more popular. The thought was, however, that the transition will be done by choic…

How has COVID-19 affected legacy code based systems, and what do we do to address the issue? Today we talk with Joao-Pierre Ruth, a technology journalist at InformationWeek where he covers DevOps and…

Knowing how to prioritize tasks and how to eliminate unnecessary assignments is a crucial skill for successful project management. The more complicated project is, the less obvious its priorities are…

We often talk about the makers and menders dichotomy on this show. But we rarely dived deep into the dynamics of collaboration between these two groups of creatives. Today we talk with Brandon Lewis …

As menders working with legacy code, we are focused on identifying and reducing technical debt. But how much easier this task would be if the creator of the code or the previous maintainer left us so…

Most, if not all, of the legacy projects feature monolithic application architectures. However, moving to containers can bring many benefits: consistency down the pipeline, no-touch deployment, bette…