I refused the rewrite and kept the stack
I kept the old stack after verifying the operational risks and adding small guardrails so the business could keep shipping.
Read article →Blog
Field notes
What I learn shipping WordPress, Laravel and automation work, written so you can act on it.
A backup you have not restored is a story
A green backup job is a claim. I believe it after a scratch restore, a login, and a file that…
Read article →
Keep the stack that already holds the business
A shop that already takes orders does not need a new framework. I choose the stack that keeps the next…
Read article →
Design for the webhook that arrives twice
The second copy of a payment event is not new work. A unique key, an outbox, and a void that…
Read article →
When the library has no passage, the model should refuse
A fluent answer with nowhere to click is the bug. The systems I run cite the passage, or they stop.
Read article →
Count a week of busywork before you buy a tool
The confident guess about where the hours go is usually wrong. I count for a week, then automate the winner.
Read article →
A green uptime light can hide a broken checkout
The homepage can return 200 while a promo code, a shipping zone or the purchase event is already losing orders.
Read article →
The WordPress move starts before the copy
The file transfer is the easy afternoon. The migration is the inventory you wrote the day before anyone touched DNS.
Read article →