Notes from the modernization trenches
What actually happens when companies try to leave the mainframe: the pitfalls, the broken promises, the economics that reward failure — and what demanding real proof looks like. Written by the people who prove parity byte-for-byte.
2026-09-14 · cobol · economics · procurementMainframe MIPS bills and the economics of standing still
The mainframe invoice goes up every year whether you change anything or not. That rising baseline creates urgency — and urgency is where procurement mistakes happen. Here is what an honest cost comparison looks like, and why most skip it.
2026-09-13 · procurement · cobol · riskThe 5-year modernization that could have been 18 months: sequencing sins
Blown modernization timelines rarely come from one disaster. They come from a plan that serializes work that could have run in parallel, and treats an open-ended exit condition as a fixed-length phase.
2026-09-13 · government · cobol · procurementGovernment modernization post-mortems: what the audit reports keep repeating
Auditor-general reports from three continents keep finding the same five structural defects in failed modernization programs. The findings are public, the pattern is clear, and the next RFP usually ignores both.
2026-09-11 · testing · cobol · riskNegative controls: how to know a green test suite isn't lying to you
A test suite that has never failed hasn't proven the conversion works — it may just have never been given a reason to fail. Negative controls are the cheap check that tells the difference.
2026-09-10 · cobol · parallel-run · testingWhat byte-exact parity actually means (and what it rules out)
"Parity" gets used to mean anything from a clean demo to bit-for-bit matched output. The gap between those two claims is where modernization budgets quietly disappear — here is the narrow, checkable version worth putting in a contract.
2026-09-03 · procurement · cobol · buyers-guideReading a modernization RFP like an engineer: 10 questions that expose the bid
Case studies and maturity slides tell you what a vendor wants you to notice. These ten questions, asked in writing before a shortlist, tell you what the bid is quietly not answering — and predict the change orders before the first invoice.
2026-09-02 · procurement · cobol · riskThe descope spiral: how "done" shrinks until failure is renamed success
No modernization program admits it failed. Instead "done" quietly shrinks, feature by feature, until whatever shipped fits the definition — and the gap becomes someone else's problem to work around forever.
2026-09-01 · cobol · vendor-lock · procurementVendor-lock runtimes: when "modernized" means hostage in a new building
Retiring the mainframe is supposed to end the dependency. Route the code through a proprietary conversion runtime instead of a real language, and you've just moved the hostage into a newer, shinier building with the same locks on the doors.
2026-08-31 · cutover · cobol · riskCutover Russian roulette: big-bang migrations and who really carries the risk
A single go-live weekend looks like a milestone on a project plan. It's actually one enterprise-wide bet placed after the vendor has already been paid — and the vendor isn't the one who answers for it if it fails.
2026-08-30 · testing · cobol · riskSynthetic test data vs. production bytes: where parity theater hides
A green test suite built on hand-written or generated inputs proves the vendor understood their own test data. It doesn't prove they understood your system. The risk was always hiding in the records nobody thought to write by hand.
2026-08-29 · cobol · parallel-run · procurementThe lost-documentation myth: the system IS the documentation, if you can prove parity
"The documentation is gone" gets treated as a blocking crisis that justifies months of reconstruction before real work starts. The running system was always the more reliable source — you don't need to rewrite it in English, you need to prove parity against it.
2026-08-28 · procurement · cobol · industryWhy rescue consulting out-bills the original project: incentives 101
A stalled modernization should make the fix cheaper — the requirements are known, some work is done. Instead the rescue engagement routinely costs as much as the original. Here's the pricing logic that makes that predictable, not accidental.
2026-08-27 · cobol · cloud-migration · riskLift-and-shift's dirty secret: same system, new rent, plus an exit fee
Moving a mainframe workload to hosted or emulated capacity feels like modernization. Usually it's the same COBOL, the same risk, and a new metered landlord who priced the deal around how expensive it is for you to ever leave.
2026-08-26 · ai · cobol · riskAI translation of money code: a lottery ticket sold as methodology
Reading unfamiliar COBOL with AI assistance is a legitimate use of the technology. Letting a model generate the replacement logic that will run in production, and calling that a methodology, is a different thing wearing the first thing's credibility.
2026-08-25 · cobol · testing · procurement"It compiles" is not a milestone: paying for behavior, not artifacts
A conversion that builds clean and demos well can still be wrong on every path nobody thought to check. Here's why artifacts are what gets billed, behavior is what actually matters, and how to make a contract pay for the second one.
2026-08-24 · parallel-run · cobol · riskThe code freeze that never holds (and how to plan for a moving legacy)
Every modernization plan has a code freeze in it. Almost none of them survive contact with a production system that has to keep processing the business's changing rules while the migration is underway.
2026-08-23 · contracts · cobol · procurementFixed price, moving target: anatomy of the change-order machine
"Fixed price" sounds like the buyer's protection. On a mainframe modernization it's usually the setup — the mechanism that turns every discovered requirement into a paid amendment, on schedule, for years.
2026-08-16 · parallel-run · cobol · riskThe eternal parallel run: why "almost matching" is the most expensive phrase in IT
Parallel run is supposed to be the safety net before cutover. It becomes a treadmill the moment nobody defines what "matching" means before the clock starts — and the meter never stops.
2026-08-15 · cobol · workforce · industryThe COBOL scarcity story: a real problem wearing a grifter's price tag
COBOL expertise really is aging out — that part isn't hype. What vendors sell you in response usually isn't a fix for that risk, it's a way to profit from it staying unsolved.
2026-08-02 · modernization · cobol · industryThe modernization grift: why mainframe rescues keep failing
Legacy modernization has a dirty secret: the economics reward failure. Here is the anatomy of the grift — the pitch, the unravel, the rescue-of-the-rescue — and the one demand that ends it.
2026-08-02 · buyers-guide · cobol · due-diligenceDemand proof before you sign: a buyer's checklist for COBOL modernization
Eight things to demand from any modernization vendor before a dollar moves — and the red flags that predict a blown budget years in advance. If they can't show you #1, walk.