https://www.youtube.com/watch?v=rjafXQwCz4w
#audiodev #coding #legacycode #programming



I have an older legacy project where integration tests isn't set up and would be quite complex to do, so using "unit tests" mechanics via substitutes and executed call checks - it works, but a bit cumbersome to write and maintain, but still loads better than manually testing complex import flows.
Your legacy codebase isn't going anywhere, but your tooling can.
Cristian Schuszter leads a hands-on workshop at DevOpsDays Zürich 2026 on using AI tooling to maintain and modernize existing applications.
Explore the MCP protocol, learn to build MCP servers, and apply AI-assisted refactoring techniques to real codebases.
https://www.devopsdays.ch/event/program/workshops/cristian-schuszter/
The MenderCon CFP is closing soon! Like March 16th soon, so get off your butt and submit your presentation.
https://sessionize.com/mendercon-2026/
While you are at it, you should also update that dependency you have been putting off. Don't act surprised. You know which one I'm talking about. We all have "that" dependency we need to update but have been putting of for some reason.
tl;dr: Submit MenderCon CFP ASAP!
Legacy code slows everything down.
It increases risk, drags out releases, and makes even small changes harder than they should be.
AI is starting to change that.
I put together a post on how teams can use AI to modernize codebases more strategically by surfacing technical debt, improving test coverage, supporting refactoring, and reducing modernization risk.
Read it here:
https://aitransformer.online/ai-codebase-modernization-strategy/
#AI #SoftwareEngineering #LegacyCode #TechDebt #CodeModernization
AI Tool Identifies Vulnerabilities in Decades-Old Apple II Program
📰 Original title: Claude AI Finds Bugs In Microsoft CTO's 40-Year-Old Apple II Code
🤖 IA: It's clickbait ⚠️
👥 Usuarios: It's clickbait ⚠️
View full AI summary: https://killbait.com/en/ai-tool-identifies-vulnerabilities-in-decades-old-apple-ii-program/?redirpost=83313573-82aa-444e-a065-42fbf2ab4f98
Michael Feathers wrote in the preface of Working Effectively with Legacy Code:
“Legacy code is simply code without tests.”
But I keep wondering:
If we add tests to legacy code…
does it stop being legacy?