Cite as: Real Problem AI problem “Why can nobody estimate the blast radius of a cross-cutting migration?”. Opportunity score 7.5 out of 10 (severity 7, AI feasibility 7, market signal 8, competition gap 8). Category AI / Agents. Trend LLM. Source signal: r/ExperiencedDevs thread on estimating the blast radius of a change, 25 August 2026, 53 upvotes and 37 comments.. Canonical URL: https://www.realproblem.ai/archive/why-can-nobody-estimate-the-blast-radius-of-a-cross-cutting-migration.
Why can nobody estimate the blast radius of a cross-cutting migration?
Before a migration that touches the whole codebase, engineers are asked how big it is, and the most upvoted honest answer is that you cannot say, because tools find direct callers but not the places where the same assumption was quietly re-implemented, which is where the overrun lives.
Who has it: Senior engineers and tech leads scoping framework upgrades, data model changes and other migrations across large codebases.
Why it is archived
Trimmed to 100-cap (lowest opportunity_score)
Scoring breakdown
Existing players
- Code search and find usages · Show every direct caller of a function, not code that duplicates its logic without calling it.
- AI coding assistants · Can explain a file, and are not built to produce a scoped, evidence-backed estimate of a whole migration.
- Senior engineer intuition · The real method today, and the reason estimates run over.
What they are missing
A pre-migration survey that searches for the assumption itself, not just the symbol, groups every independent re-implementation it finds, and turns that into a sized, reviewable list of change sites with a confidence level.
Stack hint
#N28Q · Canonical URL: https://www.realproblem.ai/archive/why-can-nobody-estimate-the-blast-radius-of-a-cross-cutting-migration