151: Software Bills of Behavior with Andrew Hendela
Simply knowing what is in your software is not any guarantee of safety. We need to know what that software does versus what we expect it to do. We need to know its rules of behavior.
Simply knowing what is in your software is not any guarantee of safety. We need to know what that software does versus what we expect it to do. We need to know its rules of behavior.
In the age of rising AI, we cannot neglect the topic of the social and political consequences of the code we leave behind.
Automating refactoring and code transformation is a fascinating and efficient way to eliminate technical debt.
Imagine if you could counter ransomware by exploiting it to create a backup of your attacked data for you. Now, that would be disruptive! Today, we talk with Lance James.
Going from monolith to microservices is one of the most popular topics in software engineering. But jumping the boat without understanding why can be a dangerous (and expensive) adventure.
Microsoft invited the Legacy Code Rocks team to attend Microsoft Build Conference and gave us access to the studio on the third floor of the Seattle Convention Center.
Microsoft invited the Legacy Code Rocks team to attend Microsoft Build Conference and gave us access to the studio on the third floor of the Seattle Convention Center.
Microsoft invited the Legacy Code Rocks team to attend Microsoft Build Conference and gave us access to the studio on the third floor of the Seattle Convention Center.
How many of your passwords do you actually know? Now, how many of those passwords are already on the black web?
There is some disconnect between business people and engineers when talking about technical debt.