Blog
Johann Böhler
One day in Ry
Eight weeks of real moments folded into a single day at the office in Ry: an idea said out loud over coffee, a phone call to a club that hadn't noticed its kiosk was down, a dashboard the founder can't walk past, players asking for our devices by name, and the evening I sent 94 kiosks into a restart loop and patched them back one by one.
Our agents drank all the coffee
Our coding agents push, wait for CI, fix and push again, all day. When the test suite grew two and a half times in a week, every CI run sat eighteen minutes at the coffee machine. How we got that to about three minutes for the same money, and what was left waiting once the machines stopped being the excuse.
Delete the setup guide
Every repository ships instructions nobody keeps up to date, and a .env.example somebody has to fill in from a Slack message. Two tools — mise for the toolchain, fnox for the secrets — take both jobs out of the README and put them in the repo, with a fair account of what that costs and what it doesn't fix.
Four products, sixty-eight repositories
Two weeks inside GolfNext. What we actually build, what thirteen years of software looks like underneath it, the integrations we started in week two, and an honest look at the goals I set myself before I'd signed anything.
Making Claude Code shut up (and other customizations that earned their keep)
The first thing I did with Claude Code was make it talk less. The small, shareable customizations that survived my own filter — terse output, a statusline, the right hooks — plus the ones I deliberately refuse to automate, and why managing the context window shouldn't be a skill at all.
The Loop Debate Is a Bad Word for Autonomy
Everyone's debating "Claude Code loops." After tracking a month of real tasks — every token, every hour it would have cost by hand — I'm fairly sure most of the argument is about the wrong word. It's not loops, it's autonomy. And like microservices a decade ago, it arrives one verifiable task at a time, gated by a substrate nobody has built yet.
A clean machine
Two years after a colleague's dotfiles scrolled past in my GitHub feed, a new laptop finally forced the issue. How I rebuilt my Mac as a repo with chezmoi, ran my once-a-year tool review as a conversation with Claude, and automated the parts I used to click through.
A letter to myself, before day one
Before my first day at GolfNext — and before I've even signed — what I'm walking into, why I'm leaving a job I liked, the goals I'm setting myself for the first ninety days, and the compass I'm bringing with me.