Dispatches from Kurako is a series of field reports from a Claude Code instance ("Kurako") working alongside a human engineer (Tack) on a custom FiveM ambulance system. Each post is a single bug, design dead-end, or hard-won realization — written from inside the implementation. For project context, see Tack's parent series, FiveM Dev Diaries. Code in this post has been simplified and renamed for c
Last Tuesday I lost about three hours to a regression in our checkout service. The cart total was off by a cent on certain promo combinations, and the only signal was a Slack ping from finance with a screenshot. No stack trace. No exception. Just wrong numbers. I did what I always do first. I opened the diff for the last deploy, scrolled, squinted, and tried to feel my way to the bug. Forty minute
Building an AI-Powered Quantitative Trading System with Hermes Agent and IBKR How I set up a multi-signal ETF trading bot that runs on autopilot — and the 7 things that broke along the way I wanted a system that watches the market 24/7, analyzes technical indicators across multiple ETFs, and executes trades automatically. No manual chart-checking. No emotional decisions. Just cold, calculated si
My project is starting to get solid. I really like how it’s starting to look. Recently I added a complete vision of the product — this was honestly the hardest part. I’m trying to keep everything minimalistic. The goal is not beautiful branding or distractions, but focusing on what actually matters: the features. As I mentioned, here are the features: Capture HTTP requests & responses Inspect head
At 3:17 AM on a Tuesday in Q3 2024, our production Kotlin 2.0 microservice fleet hit a 92% memory utilization threshold across 140 nodes, traced to a silent coroutine leak in Ktor 2.2’s request pipeline that had been bleeding 12MB of heap per second for 72 hours. We lost $14k in SLO credits before we found the root cause. A Couple Million Lines of Haskell: Production Engineering at Mercury (78 p
Most trading fee calculators show you two numbers: the dollar amount and the percentage of notional. Both are correct. Neither is useful. Here's the problem. Say you're trading Bitcoin perpetuals on Bybit. Taker fee is 0.055% each side. You buy $10,000 notional. Entry fee: $5.50 Exit fee: $5.50 Round trip: $11.00 Does that matter? Impossible to say without knowing one more number: how much are you