Pro Algo Trading | AlgoKing
Recent
may cycle setup: scanning the iv surface, automating strike selection
·1982 words
2:30 AM. wednesday.
april is basically wrapped. last weekly expiration cleared friday. monday was flat, tuesday had one small SPX position that ticked through on delta and I let it ride — closed today for +$1,100. running estimate: april MTD somewhere around +$16,500 when everything settles. YTD is going to land around +1.5%.
execution quality tracking: slippage attribution across 40 algo positions
·2014 words
2:45 AM monday.
A. went to bed around midnight after spending the evening fighting a client’s postgres migration that kept deadlocking under load. she was frustrated, said goodnight, gave me a look that meant don’t be up all night. I said I wouldn’t be.
saturday - dr r, sixteen days, halfway there
·677 words
had therapy thursday. told her about the anniversary coming up.
the session # dr r picks things up fast. i mentioned it almost as an aside - “may 11, sixteen days, we’re planning something” - and she stopped the whole thread we were on about integration and just looked at me.
april theta harvest: weekly closed clean, colo queue backed up, thursday hit different
·1534 words
2:30 AM. friday night.
A. made chicken marsala — she does it maybe once a month and I forget every time how good it is. ate around 7, she went back to her desk, lights off in the bedroom by midnight. apartment’s quiet. been staring at P&L since 11.
nq momentum signal: adaptive lookback after the tariff vol test
·1975 words
2:30 AM wednesday. A. finished something around 1 and went to bed still holding her coffee mug. found it on the counter half-full when I went for water. she’s like that when she’s in flow — stops the world when she figures it out.
replaying the yen carry unwind: validating sqs against a real vol event
·1724 words
2:15 AM monday. system’s been clean since the websocket IV fix went live friday. heartbeat healthy, colo latency normal, no stale data flags. spent most of sunday going deep on something i’ve been meaning to do since the tariff postmortem.
saturday - bookshelf drama, lesson five, the laundry room
·636 words
the bookshelf arrived thursday.
if you read last week’s post, you know this was inevitable. she’d been campaigning for it since february, and the moment i said “fine, order it,” she had already ordered it. turns out she ordered it three days before that conversation. the campaign was just waiting for me to catch up.
fixing the stale iv problem: thetadata websocket streaming for real-time greeks
·1745 words
2:30 AM friday. been at this since 9 PM.
promised myself two weeks ago, right in the middle of the tariff chaos, that i’d actually fix the IV rank staleness issue. the signal quality scoring work was the band-aid — a composite gate that tells the system “this signal isn’t reliable right now.” it worked. it’s in production. but the underlying problem was unchanged: during the spike, my IV rank was being computed from options data that was 10-14 minutes old. the signal wasn’t wrong, technically. it was just answering a question about a market that no longer existed.
signal quality scoring: building a market-aware trade gate
·2060 words
2:15 AM wednesday. apartment quiet. A. went to bed around midnight — she had a client deadline today so it was a long one. checked the colo heartbeat before sitting down to write this. normal. algos running clean for the first time since last monday.
tariff week post-mortem: what the data actually showed
·1510 words
2:30 AM monday. week one of what i’m calling “the post-tariff-chaos era” starts in a few hours.
last week was one of those that splits into a clear before and after. monday and tuesday felt like freefall — VIX went from 20 to 32 in about 36 hours, SPX dropped hard, options spreads blew out 3-4x, and my event risk throttle (which I built the week prior and wrote about here) was earning every line of code it took to build. then wednesday happened. whoever made the tariff pause call did it at 1:07 PM eastern and watching the S&P rip 8% in ninety minutes while running algorithms was… a lot.