The System Flashed a Drawdown, and I Started Counting Workdays

I run a small automated position-sizing system on the side — my own strategy, my own entry and exit rules. I don't touch it day to day; when a signal fires, it trades on its own. The idea behind building it was simple: take the "should I sell right now" call out of my own hands. Set the rules ahead of time, hand the execution to the program, and stay out of the way.

Last Wednesday, around eleven at night, I opened the dashboard like I usually do to check the day's curve. It had dipped noticeably deeper than usual. I didn't touch anything — the system didn't need me to. But I sat there staring at that negative number for almost ten minutes. The first thought that came wasn't "should I cut the position." It was a different question: how many more days of work would it take me to earn that back.

Once that calculation starts, it's hard to stop. I lined up the day's drawdown against a day's income and compared them. The number wasn't dramatic, but the moment I did the math, my stomach tightened. I was groggy at work the next day, replaying that curve in my head twice. That evening, when the system's signal came due, I stared at the prompt for a few seconds before letting it run as normal.

I've come to accept this: once that mental math starts, the hand that's supposed to hold the position loosens, and it has nothing to do with how much willpower you have. The system can stop me from placing a manual order. It can't stop me from doing the arithmetic in my head. By the time I'm done, I'm no longer in the same calm state I started in. That's exactly why I bothered building this automated system in the first place — I don't trust my own judgment once that number starts running through my head.

The system exists precisely to hold that hand back. It enters and exits on signal, indifferent to my mood that day, indifferent to whether I did the workday math the night before. It can hold back my hand. It can't hold back those ten minutes I spend staring at the dashboard, and that's the real point where the system breaks down. Not a code bug. Me, outside the rules, quietly opening a second, psychological ledger.

I've roughly worked out when that calculation doesn't kick in: if a single drawdown stays under half a month's income, I can look at it completely straight-faced. Once it crosses that line, those ten minutes happen every time, without fail. So eventually I just lowered the cap on any single position to stay under that line, not because the strategy got more conservative, but because I finally understood what I can't handle once that arithmetic starts.

The system's log never records those ten minutes, just the signals and the fills. But next time the curve dips again and I'm staring at that number, whether I check the strategy first or start counting workdays first is a question I still don't get right every time.