|
DELIVERY
Tech Delivery
Delivery is the unglamorous craft of getting software into production
and keeping it there: platforms, reliability, migrations, and leaving
a trail for the next person.
A stack a tired colleague can still run at 2 a.m. beats a clever one
only the original author understands. Hope is not a rollback plan.
|
|
| 2 a.m. tests |
- Can a new teammate find the runbook without pinging Slack folklore?
- Can we reverse tonight’s change without a hero?
- Can we name who approved the cutover?
- Does monitoring match the promises made in the design review?
- If the migration stalls halfway, is communication part of the release?
|
|
| What I favour shipping |
- Boring defaults. Clarity and observability over fashion.
- Migrations with a way back. Rollback, ownership, and a message ready before flip.
- Instrumentation first. Answer “what changed?” before the incident bridge opens.
- Finish the edges. Docs, runbooks, dull seams — trust lives there after the demo.
|
|
|
OPS NOTE
“Ship it. Leave a trail. Prefer systems a tired colleague can still operate at 2 a.m.”
That standard is kinder to users than any launch banner.
|
|
|
|
|
| Special Offer |
|
FREE
Intro call / coffee chat.
No hard sell. Just talk shop
— agents, governance, product.
|
|
|
|
|
|
|
|
|
|
|
|
|
N
Optimized for
Netscape Navigator
|
|
|
Mac
Platinum UI
c. 1996
|
|