Notes on legacy .NET migrations, system integrations, and software projects that need rescuing, written up from the engagements they came out of.
August 4, 2026
The documentation makes the migration look mechanical. On a production system it is a new project that reuses code, and verification is where the schedule goes.
ReadJuly 28, 2026
Outside help fixes a capacity shortage cleanly and a knowledge shortage only if structured for transfer. Misdiagnosing which you have is where money goes.
ReadJuly 28, 2026
Four causes account for most schedule overruns, each with a distinct signature. Scope creep and communication issues are categories, not diagnoses.
ReadJuly 21, 2026
3E, Aderant and Elite hold the canonical client and matter record. Integrations touching them inherit matter lifecycle state, fiscal period logic, and rate confidentiality.
ReadJuly 21, 2026
Rescuability depends on two conditions: the completed work represents real progress, and the remaining scope is now accurately understood. Spend to date is not an input.
ReadJuly 14, 2026
Clinical outcome reporting requires that a correct chart also produce a correct conclusion. Suppression and dual audiences are architecture, not styling.
ReadDescribe the system and where it's stuck. You'll get a straight answer about what the work involves, including if the answer is that you don't need to hire anyone.
Get in touch