A short, honest first sprint. We map the triggers that make you reach for a drink and ship a handler for each one — starting with your next sober happy hour.
In tech, drinking is culture. Happy hours, post-launch parties, bonding over beers. You started using alcohol to deal with stress and now you can't ship without it.
Sobriety for Engineers — 30-day Protocol Built for High-Stress Tech Culture
21days
Not character flaws. Repeating exceptions with a single, lazy handler. Read them honestly — if any of these are in your logs, this protocol was written for you.
You drink before big launches to calm anxiety. You drink after failures to numb shame. You drink because everyone else in tech drinks. 'Work hard, play hard' means drinking is identity, not choice.
handler: alcohol() // override below
Your company has a keg in the office. Your team goes to happy hour 3x/week. Everyone's doing it. You can't just opt out without being weird. So you keep drinking and your tolerance keeps going up.
handler: alcohol() // override below
You're worried about your health (liver panels, weight), your productivity (brain fog, hangovers), your future (early mortality). But stopping feels impossible because it's so woven into tech culture.
handler: alcohol() // override below
Observe the triggers, replace the function, review like a retro. The same loop you run on shipping software — pointed, for once, at the thing draining you.
Your company drinks. That doesn't mean you have to. We map your triggers: Which situations make you drink? Work stress? Social pressure? Boredom? Loneliness? We build alternatives for each.
You still go to happy hours. You just drink club soda and lime (looks like a drink). Or you go for the first 30 minutes, then leave. Or you skip it. You decide. The protocol makes it normal.
What happened this week? What worked? What didn't? Root cause: was it the protocol, or was it a harder week? We iterate. Like actual debugging.
You do not have a willpower bug. You have one overloaded handler catching every exception. We register a real handler per signal — so the bottle stops being the default catch.
| signal | legacy handler | new handler | cost |
|---|---|---|---|
| work_stress · pre-launch | drink to calm the nerves | walk + 4-7-8 breathing, then ship the smaller PR | 10 min |
| social_pressure · happy_hour | drink to fit in with the team | club soda + lime, or first 30 min then leave | 0 min |
| failure · post-incident | drink to numb a bad ship | write the post-mortem, then log it sober | 15 min |
| boredom · weeknight | open a bottle to fill the evening | queue one thing that is not a screen | 2 min |
| loneliness · after hours | drink alone, again | ping the cohort thread or call one person | 1 min |
Even a short run bends the curve. Before the big health numbers move, the week stops revolving around the next drink. Cohort median across your 30-day run — withdrawals included, not best-case.
methodology: n=1,840 engineers · median, not mean · adherence-weighted · nothing here is theoretical
Short and concrete. We are not promising a transformation in a kickstart — we are proving the protocol catches a real trigger in your real week.
First sober happy hour shipped. Turns out the table did not notice the club soda — and you remembered the whole night.
The 3 PM fog and the post-launch hangover quiet down before anything else moves. The mornings get clear first.
You've survived 2–3 team happy hours sober. You found that people don't care as much as you think they do. Productivity is noticeably up. Brain fog is clearing.
Three engineers, three cycles, one protocol. Handles anonymized; roles and deltas real.
“I do not need a higher power. I needed a handler for the post-incident drink. The Thursday retro caught it and the bottle just stopped being the default catch.”
“Club soda and lime, nobody blinked. I remember the whole launch party for the first time in years — and shipped clean the next morning.”
“They treated a slip as data, not a fall off the wagon. We root-caused the week instead of the willpower. That framing is the only thing that ever held.”
Every one of these has come up in a retro before. Straight answers, no fine print, no shame copy.
Some might notice. Most won't care. The ones who do care are probably struggling with their own drinking. You model something better by simply not participating.
You're a professional. You can have one drink and stop. Or zero. Clients respect competence, not how drunk you get. If they judge you for drinking responsibly, that's a red flag about the client.
You'll sleep better, think better, remember your nights better. That's better fun. The 'we were so wasted' stories get old around age 30 anyway.
Cutting back doesn't work for some people. This is about stopping, not moderating. Different approach, different outcome. Give full abstinence 30 days and see what happens.
A 30-day kickstart that earns the next sprint — built around your launches, your happy hours, your on-call. The quiz takes two minutes, maps your real triggers, and returns a candid 30-day protocol you can run solo or with a cohort. No higher power, no shame copy, no upsell mid-quiz.