Semicolon Softwarehttps://semicolonsoftware.com/Notes on maintainable software, controlled releases, dependency evidence, and incident learning.Choose a module boundary from change pressurehttps://semicolonsoftware.com/notes/module-boundaries/https://semicolonsoftware.com/notes/module-boundaries/Group behavior that changes for the same reason and expose a narrow contract around it.Design rollback before the release artifacthttps://semicolonsoftware.com/notes/release-rollback/https://semicolonsoftware.com/notes/release-rollback/Keep code, configuration, schema, and queued work compatible with a reversal.Upgrade a dependency with evidencehttps://semicolonsoftware.com/notes/dependency-upgrades/https://semicolonsoftware.com/notes/dependency-upgrades/Separate security urgency, API compatibility, runtime behavior, and deployment risk.Write an incident review that changes the systemhttps://semicolonsoftware.com/notes/incident-review/https://semicolonsoftware.com/notes/incident-review/Build a factual timeline, identify control gaps, and assign improvements with verifiable completion conditions.Model a trading request as a state machinehttps://semicolonsoftware.com/notes/trading-api-request-state/https://semicolonsoftware.com/notes/trading-api-request-state/Handle authentication, submission, acknowledgement, finality, retry, and reconciliation without turning an uncertain response into a duplicate action.Draw telehealth workflow boundaries around patient statehttps://semicolonsoftware.com/notes/telehealth-workflow-boundaries/https://semicolonsoftware.com/notes/telehealth-workflow-boundaries/Keep intake, eligibility, scheduling, clinical review, prescribing, fulfillment, and support from sharing an ambiguous status.