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
Clinical outcome reporting requires that a correct chart also produce a correct conclusion. Suppression and dual audiences are architecture, not styling.
Read: What Makes Healthcare Data Visualization Different from Standard ReportingJuly 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.
Read: We Inherited a .NET Codebase Nobody Understands: Where Do We StartJuly 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.
Read: What to Do When Your .NET Developer Leaves Without DocumentationJuly 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.
Read: iManage Upgrade Planning: What IT Directors Need to Account ForJune 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.
Read: What Changes When the Original Developer LeavesJune 23, 2026
A non-technical buyer can evaluate technical judgment structurally: which way the conversation moves, what is asked, whether the estimate decomposes.
Read: How to Evaluate a Software Consultant Before You Sign AnythingDescribe 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