Case studies
Case Study: Rescuing an End-of-Life WordPress Server (Debian 9 to Debian 12) and Adding HTTPS
How a five-year-old WordPress server on end-of-life Debian 9 was rebuilt on Debian 12 with HTTPS, a new server and the same IP address, and how the old servers were retired.
From inherited code to a documented, tested, load-tuned system in about five weeks
One engineer, two inherited legacy PHP applications and no handover: how documentation, tests and a load-tuned configuration came out of a single conversation.
From 3,370 old posts to a versioned writing workflow in three weeks
One personal blog, about 3,370 posts and a 14 MB export: how an archive, a style guide and a git history made writing with an AI partner repeatable.
Reading a law against its own paperwork: a four-part series on the Universal Health Care Act
How four posts on the Universal Health Care Act were built from 203 official documents, 49 checked public claims and a habit of publishing dated corrections.
Turning a Supreme Court ruling into a four-part guide to the national budget
How a Supreme Court ruling on the national budget became a research note, a full read of 121 pages and 12 opinions, and a four-part explainer series now being published.
From a pile of 1,554 unreadable scans to a searchable, reconciled archive
How a read-only, nine-stage pipeline turned 28,892 pages of unsearchable scans into a full-text index, a reconciliation against the official spreadsheet and eight recommendations.
A public intake form that will not accept an incomplete proposal
A web form whose completeness gate and public guide are generated from the same rules, so the guide cannot disagree with what the form enforces.
One place for proposals, cases, approvals and the asset registry
Three connected prototypes for a government disposition office, built from its rules and checked against its real paperwork: asset registry reports, a proposal register and a case tracker with computed deadlines.
Planning a forced vendor transition in two days: from four versions of one app set to a gated, dated plan
How a contract constraint became a scoped plan, a schedule, a leadership deck and a first working REST service, with every capability claim checked against the code.
Running a 13-service hospital system locally on PostgreSQL, without touching patient data
Porting production Laravel code from MySQL to PostgreSQL, rebuilding its schemas safely, and proving it with 43 working report PDFs from fictional patients.
Replicating a city health center database into BigQuery: from a change-data stream to a privacy-split dashboard
Moving production health data into an analytics warehouse in staged, reversible steps, with the personal data separated by authorized views before a one-page dashboard was built on them.
More case studies to come. For my full background, see my resume.