Blog
How we're building GolfNext
Engineering, operations, and infrastructure at a small, ambitious team. How we solve problems and scale intelligently.
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.
No posts found.