Personal Ops
Notes on building a personal operating system: the Telegram bot, the failure modes it walked into, and the slow rebuild toward something firm but yielding. Engineering pointed squarely at my own executive function.
Part 1
Personal Ops: Capture, Digest, Adapt, Propose
May 28, 2026Two years ago my Elul accountability experiment half-worked. The problem was friction, not motivation — and I had no mechanism to adjust expectations based on actual performance. So I built one: voice capture via Telegram, weekly LLM digest, and a daily agenda calibrated to what I've actually been completing versus missing.
Part 2
Don’t Clip Your Wings: On Building Systems That Push You Toward Greatness
May 31, 2026Completion rate is a trap. The moment your productivity system scores you on what percentage of commitments you finish, the rational move is to stop writing down anything you might actually fail at. I ran into this building my own personal ops system, and it turns out fixing it means thinking about Item Response Theory, Glicko ratings, and the Sharpe ratio.
Part 3
Reed, Not Cedar: Building a Productivity System That Bends With You
Jun 2, 2026I built a Telegram bot to offload my executive function and accidentally gave myself a taskmaster. So I rebuilt it around one rule from the Talmud and the Daode Jing: be a reed, not a cedar — firm but yielding, advisory not prescriptive.
Part 4
Count First, Interpret Second
Jun 2, 2026My personal-ops bot's weekly digest kept turning noisy logs into confident diagnoses. The fix was one rule: count first, interpret second, diagnose cautiously.