Notes on legacy .NET migrations, system integrations, and software projects that need rescuing, written up from the engagements they came out of.
July 14, 2026
A structured first 60 days on an inherited .NET codebase: get it running, trace workflows, map risk concentration, and defer every architectural judgment until the map exists.
ReadJuly 7, 2026
The first thirty days after an undocumented departure are reconnaissance, not cleanup. Four inventories establish what exists before any change creates an outage.
ReadJuly 7, 2026
An iManage upgrade timeline is set by the integration inventory, workspace configuration and search validation, none of which are in the vendor guide.
ReadJune 30, 2026
Code survives a developer's departure. Intent, the inbound dependency map, and the operational baseline do not, and each has a distinct recovery cost.
ReadJune 23, 2026
A non-technical buyer can evaluate technical judgment structurally: which way the conversation moves, what is asked, whether the estimate decomposes.
ReadJune 16, 2026
Law firm project overruns come from decision latency, outside counsel security review, and thirty years of client data, none of which appear in generic technology estimates.
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