That was a great early lesson to never trust code you read online. Even if it is from Microsoft’s own developer portal.
I start my workday late, around 11. I sit at my desk and shake the mouse - nothing.
“huh, that’s weird. why is this stupid thing not starting up?”
I press a few random keys on my keyboard - nothing.
I push the fingerprint sensor - nothing. “seriously?”
I tap on the trackpad. No haptic feedback. Completely unresponsive. “maybe there is something loose from cable managing last night?” I check the cables, everything’s plugged-in.
I try to force restart the computer, but it’s warm… no, it’s hot. “that’s weird.”
My stomach sinks. I had spilled tea all over this computer a few months ago. The bottom chassis was replaced, but maybe something hadn’t been. My next on-call shift is coming up in three days. “ugh,” I think.
“macOS 26 has been unreliable, it did update 2 nights ago.” It shuts down fine, I let go, I press the button again, it starts up fine.
I log in, start a terminal up, type in claude, press return. I want to see what I need to do using /adhd.
It starts to slow down, again. Even cd is crawling. “huh.”
I open Activity Monitor and see memory pressure in the red. “that’s weird, i wonder what’s causing that.” I scroll through the processes list and see: hundreds of CC instances.
I start to put 2 + 2 together: slow computer last night, “oh,” hot chassis, “huh,” memory pressure red, “oh no no no no no,” chassis still hot, “well, shit.”
Some mistakes in life you realize right away, others go unnoticed.
This was the latter kind.
want to hear more of my unhinged rants? drop your email.
“wtf” I think to myself as my terminal starts to slow down at 2AM. “ugh, i’m going to bed, i’ll figure this shit out tomorrow.”
The SessionStart hook I’d just created spawns 2 background CC instances using claude -p ..., each of which follows the normal start-up sequence.
I get up from my desk. I walk away from my terminal for the night.
I try to force quit every instance of CC in the Activity Monitor. They spawn faster than I can kill them. ghostty + pkill will work better but ghostty is unresponsive.
The realizations continue. “SHIT SHIT SHIT” repeating in my head as my hand bolts for the power button and I force restart the machine.
“you dumbass.” I berate myself. Every instance of CC starts two more CC instances. I created a hook that causes an explosion…1 → 2 → 4 → 8 → 16 → 32 → 2^N…
I open ~/.claude/settings.json and remove the hook. I have Activity Monitor open, it’s filtering down to claude. I open another ghostty instance and type in claude. Before hitting enter, I rest my free hand’s index finger on the power button, I hit return with the other; everything’s fine, just a single instance. I breathe easy.
It took me almost two decades, but at that moment I realized I had created my first fork bomb. It had completely bricked my computer ‘cause it ran overnight.
Another realization dawns on me: “the bill.” My company has API billing. “i’m so screwed.” I open Edge, my heart pounds as the icon bounces, I go to the “Usage” page, just gone up by $600. I’m good. I calm down.
The shitty code behind CC just saved my ass. The ridiculous amounts of memory every single instance consumes ‘cause of the Bun → React → TUI chain had blown up the memory usage. It caused my computer to lock up. Shitty code combined with Claude’s caching saved me before someone in accounting would start asking questions.
This is the one and only time I’ll be thankful for software being shitty and bloated.
This was the imperfect end to an imperfect month of late night coding sessions, going down rabbit holes and building skills, hooks and frameworks.
My company had given us access to Cursor at the start of 2025. I used it heavily to research the massive codebase whenever I needed it. 311M+ tokens worth of usage.
February 2026 started with a new push for agentic workflows and programming.
I gritted my teeth. I didn’t want to write, review and maintain AI slop. I pushed back on RFCs that proposed full agentic programming loops.
Then, I figured, if this was the new expected workflow, the new meta, the new paradigm, I might as well master it. I sure as hell was not going to get left behind.
I asked for permissions to a CC account. I opened the dashboard and noticed the API pricing. “tokens go brrrrrr?”
I begrudgingly ran brew install --cask claude-code and explored. I looked on the positive side, I could finally use ghostty + nvim + tmux combined with CC for everything. No more VSCode clone with AI bits bolted on.
I experimented and found the use cases that worked well. More crucially, the rough edges. I spent too many tokens experimenting with CC. So, I decided to give a quick crash course on CC usage for my team. I wrote a doc, presented it and organized the whole week.
Powered by my ADHD hyperfocus, anxiety and spite, I built the tools that helped me and I learned a lot.
After February had passed, this was the monstrosity I built after a $3800 API bill.
/yadumb [the dumb thing it just did]Tells CC to dump what it did into a file with all the context ‘cause this random token generator breaks all the time, even when you TELL IT TO DO SOMETHING IN CAPS, BOLD AND ITALICIZED.
When a skill explicitly says:
STILL, every goddamn time, it goes through this exact sequence for that skill:
🤦 I tell it to log what it did, then go kick rocks.
/mementoRemember Leonard’s memory from Memento? No. Maybe Dory’s memory? Good, ‘cause I don’t.
I need something to log conversations. This does exactly that with a:
/yablind [-N] [path]‘Cause the context window size is the bane of this statistics output machine’s existence. The output quality gets significantly worse even at 40% usage, especially with images. Plus, I’m too lazy to copy/paste text. This tells it to call a subagent to:
[path]All in service of a single objective: Minimize unnecessary content in the goddamn context window.
/adhdMy ADHD ass can’t be bothered to check Slack, GH, Notion and only god knows what else, EVERY, GOD, DAMN, MORNING.
I’m the person who likes meetings. No, Karen, this couldn’t have been an email ‘cause I don’t read those.
To address my weakness, I created a skill to pull together a list of things I need to do and want to do, and it tries to update older items. It then tries to prioritize what’s left. For more details see this, except mine is local only.
The chart-topping bangers:
notnow - when I’m definitely answering that stupid request at 5PM on a Fridayimout - done for the day routine[others] - boring ones I won’t list.Seventeen scripts deterministically fetch the data before feeding it to the over-eager, coked-out junior (LLM) to generate:
/moneyIt forgets everything, every run. Don’t let the existence of the MEMORY.md file tell you otherwise. It doesn’t save the relevant shit and is outdated, at the same time. This EP skill comes with:
showmethemoney - show projectsgimmethemoney - dump the state and decisions into this project’s statethemoney [project id] - load project state filesThis hopefully lets it get at least part of the context from previous conversations but you’re rolling the dice just like it does!
PreToolUse/PostToolUse HookI can’t be bothered to remember my own patterns, let alone CC’s patterns. I created two hooks:
PreToolUse - Saves the contents of a Bash command. Including Python wrapped in Shell.PostToolUse - Writes a completed status with the tool_use_idBoth save to a single append-only jsonl file, organized by day. “wHy DoN’t yOu UsE tHe LoGs FrOm ~/.claude?” ‘Cause that shit is expensive as hell to analyze and I can’t save ~/.claude in version control.
The rest…TBC ✌️
/fight-to-death - A Gladiator cosplay aka Adversarial PR review.~/.claude/CLAUDE.md - the LLM has “kinks of a nympho fetish” (K.Dot).want to hear more of my unhinged rants? drop your email.