Every codebase has functions no one remembers writing. They were added late one night to fix something, they worked, and they quietly became permanent. Nobody reviewed them. Nobody documented them. They just run, every time, in the background. Your habits are the same. The evening drink after a long day of shipping code is often one of those functions. You never sat down and decided on it. It got added at some point, it worked, and it has been running ever since.
You Cannot Fix What You Cannot Observe
The first rule of debugging is that you cannot fix a problem you cannot see. Before you touch anything, you instrument the system. You add logging. You watch what actually happens instead of what you assume happens.
Most people skip this step entirely with their own behavior. They decide they want to change something and jump straight to brute force, more willpower, stricter rules, a hard cutoff. That is like pushing a fix to production with no logs and no tests, hoping it works. It usually does not, and you have no idea why.
The more useful move is boring and effective. Before changing anything, just observe. When does the drink actually happen. What is the state of the system right before it. Tired. Wired after a hard problem. Bored during a long build. Winding down from too many meetings. You are not judging the behavior yet. You are collecting logs.
Find the Trigger, Not the Symptom
Any developer knows the bug you see is rarely the bug you have. The crash is a symptom. The real cause is three layers up, in something that looked unrelated. Habits work the same way. The drink is the symptom. The trigger is somewhere earlier in the chain.
Behavior runs on loops. A cue fires a routine that delivers a reward, and the research on how habits form shows the whole sequence runs mostly on autopilot, below conscious thought. Your job is to trace it back. The reach for the glass is the output. What was the input. Once you find the actual trigger, whether it is a specific time, a specific kind of stress, or just the ritual of closing the laptop, you finally have something you can work with. Fixing the trigger beats fighting the symptom every time.
Willpower Does Not Scale
Here is a systems truth that applies neatly to habits. Any solution that depends on constant manual effort does not scale. It works until you are tired, distracted, or under load, and then it fails exactly when you need it most.
Willpower is manual effort. Relying on it to override a well worn habit every single evening is like handling a high traffic endpoint by having someone process each request by hand. It holds for a while, then it collapses. Awareness scales better, because noticing the trigger takes almost no energy once you have trained the habit of noticing. You are not fighting the loop by force. You are catching it at the input, where a small change costs almost nothing.
Refactor, Do Not Rewrite
Nobody sane rewrites a working system from scratch overnight. You refactor. Small, safe changes, tested one at a time, each one leaving the thing a little better without breaking it.
Habits respond to the same approach. You do not need a dramatic overhaul or a lifelong vow. You change one input and watch the output. Swap the automatic pour for something else on one evening and observe the result, your sleep, your focus the next morning, your mood. The connection between alcohol and disrupted sleep is well documented, and for anyone whose work depends on a sharp mind, that downstream cost is the metric that matters. Keep the changes that improve the system. Roll back the ones that do not. This is just iterative development pointed at your own life.
A Tool for Instrumentation
This is essentially what Unconscious Moderation is built to do. It is an app that uses neuroscience and self reflection to help people understand their relationship with alcohol, which in engineering terms is instrumentation for a system you cannot otherwise see clearly. It does not lecture you or hand you a rulebook. It helps you observe your own patterns without shame, so the fix becomes obvious instead of forced. For people who already think in systems, that framing tends to click faster than any amount of willpower talk.
Ship the Better Version
None of this is about deleting anything from your life or labeling yourself. It is about treating an automatic behavior the way you would treat any undocumented process running on your machine. Look at it. Understand what triggers it. Decide, with clear eyes, whether it is still serving you. Then make a small, testable change and measure the result.
You debug systems for a living. The habit you never consciously wrote is just one more process worth reading before it keeps running unattended. Add the logging. Find the trigger. Ship the better version of the evening. Your future self, the one waking up clear and shipping clean, will thank you for the patch.
