John Paul (JP) Ashenfelter Engineering Manager, BridgeCare
All shows end. All buildings end. All kingdoms end. The globe itself ends. Human life ends.
--?
Hospice starts by naming reality honestly instead of pretending cure is still the goal.
Tell users clearly that the site/app is ending, why, and when.
The goal shifts from aggressive intervention to reducing pain and preserving peace
Stop adding features and avoid risky changes. Keep the system stable
People need time and support to gather what matters before the ending.
Help users and owners get their data, reports, records, or history out.
Hospice often makes space for memory, meaning, and what remains after the person or system is gone
Preserve the final code, database snapshots, screenshots, docs, and story.
Not abandonment, but removing interventions in a planned, humane way
Turn off jobs, DNS, certs, alerts, integrations, credentials, billing, and servers deliberately.
Endings need acknowledgment; people process loss better when it is witnessed.
Mark the ending with a final note, retrospective, thank-you, or ritual
Does anyone know where this quote comes from
Tempest
THE tempest, by william shakespeare
Two years ago, I gave a talk here about my 21 year old Rails application (now 23). Purple shirt baby!
Two weeks ago, I shut it down for good.
definitely not a "pivot"
Also the end of tech debt
Based on hospice care