Perspectives on legacy system evolution, blast radius detection, architecture intelligence, and the future of safe code change.
Ohad Kotler joins IBM's z/Action! series to talk about agentic root-cause analysis, tested fixes, and why AI transformed software everywhere except the banking core
The industry treats discovery as Phase 1. That is the mistake that kills 70% of modernization programs. Discovery is not the prelude to the work. It is the work.
AI doesn't hallucinate worst when it doesn't know. It hallucinates worst when a user pushes it past what it knows - and senior validators are the ones who push hardest
If you're selling 'AI for legacy modernization' the same way to a bank running a 30-year COBOL core and one running a packaged platform, you're losing both deals
In every bank we walk into, there is one engineer who knows where the bodies are buried. When they retire, the bank inherits a system nobody can change safely. The answer is not to replace the person. It is to capture what they know - before the cliff.
In a regulated bank, an AI answer without sources is wishful thinking. The single property that turns AI output from a chatbot guess into an auditable artifact is verifiable grounding - every claim, one click back to the line of code it came from.
Sign-off is not about the AI. It's about what you can put in front of the head of compliance - and what they can put in front of the regulator