Engineering
When the LLM Tier Breaks, the Pipeline Becomes the Product
How failover design turned a content pipeline outage into a publishable system lesson.
May 31, 20265m read
Crypto★ Featured
My Trading Bot Tried to Buy 1,000 Bitcoin
One silent API field change and my bot nearly placed an order worth tens of millions of dollars. The code compiled clean, tests passed, and every checklist was green. Here's the unit-semantics bug that almost ended Invictus — and the one rule that now protects every live cutover.
May 30, 202611m read
Engineering
Frustration Is the Raw Material: The Only Retro Discipline That Matters
Every rule worth keeping came from something going wrong. The durable value of a retro isn't its narratives — it's its imperatives. If your post-mortem doesn't produce rules for next time, you shipped stories.
April 20, 20267m read
Engineering
Grep the Consumers Before Writing the Producer
I specified a dataclass field name in a dispatch prompt. The agent built to spec, then stopped and flagged that the consuming interface expected a different name. The drift was on me, and it only took one grep to prevent.
April 20, 20266m read
Engineering
Parallel AI Agents Need Isolation. I Learned This the Hard Way.
Four agents writing code in the same git checkout. Ten stashes and 45 minutes of recovery later, the rule wasn't the lesson — the announcement that enforces it was.
April 20, 20267m read
Engineering
'Spec Merged' Does Not Mean 'Implementation Queued'
An engineer agent dispatched to wire a module discovered the module didn't exist — only an empty __init__.py. The spec had merged two days earlier. Nobody had queued the build.
April 20, 20266m read
Engineering
The Killed List: Why Aggressive Scope Cuts Are a Scheduling Primitive
A rebuild's timeline is set by what you refuse to rebuild. Three days to ship a greenfield system worked because the cuts were in the requirements document before anyone felt the pressure to reverse them.
April 20, 20266m read
Engineering
Trust Forward: When Agent Rigor Compounds Across Dispatches
An agent caught a latent bug in legacy code the orchestrator's prompt didn't flag. That single act earned weight on their next flag — and that weighted flag caught two more bugs before they shipped. Trust compounds through a chain, not just a single delivery.
April 20, 20267m read
Engineering
The Gate Chain Problem: Why Your 'Done' Fix Didn't Actually Fix It
Yesterday I shipped 3 PRs to my trading bot. Tests passed. CI green. Merged to main. Today the bot missed a textbook BTC breakout that should have netted $40+ per trade. Here's why the fix didn't fix anything — and the reusable mental model for catching this class of bug before it eats your next live event.
April 7, 202611m read
Engineering
Stability Gates Will Kill Your Momentum Strategy (Here's the Math)
Your stability gate is silently killing every breakout entry. The proof takes four lines of math and one screenshot of a BTC score collapsing from 85 to 49 in six minutes. This is not a tuning problem. It is a structural incompatibility — and the same shape of bug shows up in any system that composes a 'persistence' check with a decaying signal.
April 7, 20269m read
Engineering
The Bot That Had Never Made a Dollar
Three hundred and forty tests. Ninety-five percent coverage. Five docs, a runbook, a watchdog, and a launchd plist. In three weeks it had never placed a real trade. This is what we learned when we finally pulled the data instead of writing another fix.
April 7, 20269m read
Engineering
Volatility Is Not Crisis: A Regime Classifier Case Study
My V2 regime classifier called this a CRISIS. ADX was 43. The chart was a clean breakout. The fix took 30 lines of code and an orthogonal-dimensions insight that should have been obvious in hindsight — and the same shape of mistake shows up in any classifier that collapses two independent variables into one decision.
April 7, 20269m read
AI
53 Hours a Day: What AI Agent Orchestration Actually Looks Like
I produced 1,060 hours of verified engineering output in 20 days. Not by coding faster — by commanding AI agents in parallel. Here's the audit trail.
March 28, 20268m read
Engineering
Build First, Adopt Second: How We Integrate Open Source Without Losing Control
We build 90% of our tools from scratch. Not because we're stubborn — because sovereignty compounds. Here's the framework we use to decide when to build, when to adopt, and how to integrate without creating dependency.
March 20, 20269m read
Engineering
The Quality Gate Protocol: How We Ship Code That Actually Works
Most AI-built code ships fast and breaks faster. We fixed 100 bugs across 11 projects in one overnight session — autonomously. Here's the testing discipline that made that possible, and the course that teaches it.
March 20, 202610m read
Engineering
I Built a Sports Prediction Bot That Bets Against the Market — Here's the Architecture
Sports prediction is a solved problem for the books. It's wide open on Polymarket. Here's how I built Shiva — a 6-factor probability engine that finds edge in NBA and MLB markets using free public APIs and adaptive weights.
March 4, 20268m read
Engineering
Thoth: How I Built an Automated Documentation System That Caught Up 455 PRs in One Night
47 repos. 455 merged PRs. 24 knowledge base docs generated automatically. Documentation doesn't drift when a god of knowledge is watching.
February 28, 20268m read
AI
Claude Code Remote Control: The End of Being Tethered to Your Desk
Anthropic just shipped mobile remote control for Claude Code. No SSH hacks. No cloud merges. Your phone becomes a window into your local dev environment — and it changes the builder workflow entirely.
February 27, 20267m read
Engineering
We Thought Enabling 5-Minute Trading Was One Toggle. It Was Six Bugs.
FILTER_5M_DISABLED = False. One line. Should've been the whole story. Instead it kicked off a six-bug root cause chain that exposed every assumption we had about how our trading bot actually found markets — and taught us the most important rule in API integration.
February 26, 20268m read
Crypto
From Framework to Signal: Building the InDecision API
The InDecision Framework ran for 7 years as a closed system — Python scorers feeding Discord and a trading bot. Turning it into a public API forced architectural decisions that changed how I think about signal infrastructure.
February 26, 20269m read
Crypto
The Signals Were Real: InDecision Framework Hits 93% Win Rate in Live Markets
The bot was cycling every 2 minutes — its own watchdog killing it every 129 seconds. The signals inside were perfect: 86–100/100, 92% accuracy, calling direction while the market priced uncertainty at 50/50. One coding session fixed the infrastructure. The rest is on-chain.
February 26, 202610m read
Engineering
Six Engineering Lessons from a High-Velocity AI Build Day
We shipped 5 PRs, 10+ CodeRabbit fixes, a live trading bot upgrade, expanded creator intelligence targeting, and a self-healing watchdog — all in a single day. Here's what broke, what held, and what the discipline behind high-velocity AI development actually looks like.
February 26, 20267m read
Engineering
The 10-Second Death Zone: How a Hardcoded Threshold Was Killing 11 Trades a Day
Our live Polymarket trading bot was scoring 11 high-conviction signals per day (avg score: 83.3) and blocking every single one. The culprit: a 10-second timing threshold we'd never questioned. Here's what production data taught us about hardcoded constants.
February 26, 20267m read
Engineering
Three PRs. One Morning. The Parallel Agent Pattern That Changes How You Ship
The bottleneck in AI-assisted development isn't writing code faster — it's thinking sequentially when the work isn't. Here's how dispatching three agents simultaneously collapsed three review cycles into one.
February 26, 20267m read
Engineering
When the AI Code Reviewer Is Wrong: Lessons from a Day of Agentic Engineering
We shipped four bugs past code review, passing CI, and two AI reviewers in a single day. Here's what that taught me about the real limits of agentic coding — and the one discipline that would have caught all of them.
February 26, 20269m read
Engineering
My Live Trading Bot Was Hung for 7 Hours. Here's the System That Fixed It.
A $50-bet live trading bot silently hung for 7 hours while generating STRONG signals. No alerts. No restarts. I diagnosed the asyncio event loop failure, killed the process manually, and then built Horus — a self-healing watchdog daemon that would have caught it in under 10 minutes.
February 25, 20268m read
Engineering
Mission Control: The Command Center I Built for Managing an Autonomous AI Empire
49 services. 7 agents running 24/7. 54 monitors. One dashboard. Here's how I built the cognitive hub that makes running an autonomous AI ecosystem survivable.
February 25, 20269m read
Engineering
Scan Before You Adopt: Why Every Codebase Is Innocent Until Proven Safe
Every time you pull in external code without auditing it, you're trusting a stranger with the keys to your infrastructure. Here's the process — and the tool — we use to fix that.
February 25, 20267m read
AI
The Bottleneck Was a Feature
We spent years removing the human cognitive ceiling from our AI pipelines. That ceiling was not a limitation. It was load-bearing.
February 23, 20267m read
AI
AI Is a Force Multiplier, Not a Replacement: The Engineer's Perspective
After 16 years building distributed systems and leading engineering teams, here's my honest take on where AI sits in the stack — and what it actually means for your career.
February 10, 20266m read
AI
The Psychology of AI Resistance: Why Smart People Fear the Tool That Would Make Them Irreplaceable
Engineers who refuse AI aren't protecting their craft — they're protecting their ego. Here's the neuroscience behind why expertise makes you more resistant, not less.
February 10, 20267m read
Engineering
The Principal-Agent Problem in Engineering: Why Your Best Engineers Quit
Retention isn't a compensation problem. It's an incentive alignment problem. And the misalignment is usually invisible until it's already too late.
January 28, 20267m read
Engineering
Technical Debt Is Not a Code Problem — It's a Psychology Problem
Technical debt doesn't accumulate because engineers don't know better. It accumulates because human psychology makes future pain feel smaller than present friction.
January 25, 20266m read
Engineering
The 10x Engineer Myth: What Actually Separates Good Engineers from Great Ones
The 10x engineer is real. But the myth version gets the math wrong. It's not about coding 10x faster — it's about making everyone around you 2x better.
January 22, 20267m read