Loading page
A generalized recovery pattern for an important CAD utility whose behavior remained valuable while dependencies, deployment, diagnostics, and maintenance ownership had become fragile.
Knowledge lived in source, operator habits, deployment steps, platform assumptions, and undocumented exception handling. A broad rewrite would have put trusted behavior at risk.
The recovery path required representative examples, version context, deployment constraints, source and credential boundaries, and a rollback route.
The work reduced uncertainty before introducing structural change.
Validation included output parity, exception behavior, platform-version notes, installation or deployment checks, logs, and a documented rollback decision.
The resulting pattern made the application easier to diagnose, release, and own while preserving the option to modernize additional slices only where evidence supported it.
This pattern fits AutoLISP, VBA, VB.NET, .NET Framework, desktop utilities, add-ins, scripts, and engineering applications with valuable behavior and rising support risk.
Evidence boundary: Founder-led prior work is generalized for public review. Client, employer, drawing, model, commercial, and production details are withheld; no endorsement is implied.
Start with the current behavior, accepted output, known failure cases, private-review boundary, and the first decision the engagement should resolve.