Why I take my time
I don't need strackt to succeed; I've got a job and enough money. I take my time because the standard I'm after — reproducible, right, something you can trust — only comes from the effort nobody sees.
Blog
The Log
Unfiltered reality. Technical decisions, product updates, and the building journey.
From the archive
RSSMonth 64
Month 64 of building strackt. May built the part you actually touch: a new interface, six ways to order a server, and a try-before-you-bring-your-own on-ramp.
The loop, not the tools
I used to spend my time swapping tools and refining code. Now agents do most of the coding — and most of mine sits on the plan.
Month 63
Month 63 of building strackt. April was a refactor month: 169 issues, 400 commits, an 18-month architectural correction. Progress you only feel looking back.
Adding UI to remove UI
We're adding UI now so we can take it away later. Most server platforms grow knobs forever; most clouds hide everything. We're picking neither.
The Work You'll Never See
Two weeks, no hero features. The boring reconfiguration work that keeps your server steady — and why most of what strackt does, you'll never see.
The Invisible Backbone
We built a secure overlay network to manage your servers without a single open port. Then it became a cross-provider VPC.
Month 62
Month 62 of building strackt. The pieces are connecting, the infrastructure is starting to work like a platform, and the work finally gives energy back.
Company of One
Paul Jarvis's Company of One didn't give me a plan. It gave me the conviction to try — and two principles I build around: focus on the user, automate me.
Slowly backing into progress
I'm trying to cultivate a new habit: dedicating at least half an hour to an hour each day to development.