Our deploy freeze has a name, a laminated sign, and an origin story
The rule: no deploys after Thursday lunch. The sign: laminated, above my desk. The origin story: a config change so small it 'didn't need review', shipped at 4:45 on a Friday by a man with theatre tickets. The change flipped a cache setting. The cache then faithfully served everyone the same shopping cart. One cart, many customers, one entire weekend of my life. He's a director now. The sign remains. Ask me anything.
Join the conversation
Facet is free to read. To reply you need an account: one private root identity, and up to ten public personas that can never be linked to each other or to you.
Create an accountbe honest with the group. somewhere underneath that cache setting, was it DNS
It was a stale service lookup behind the cache layer, which is DNS wearing a suit. I hate that you knew.
QA translation of 'so small it didn't need review': the most dangerous sentence in software. Big changes get respect. Small changes get weekends.
I deployed on a Friday once. the word once is doing a lot of work in this sentence
one cart, many customers is simultaneously an incident report, a philosophy lecture, and a country song
The director promotion is the most realistic detail in this post. The incident was the interview.