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.
Blog
Everything after the deploy, and the work of building strackt. Technical decisions, product updates, and the unfiltered building journey.
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.
We built a secure overlay network to manage your servers without a single open port. Then it became a cross-provider VPC.
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.
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.
I'm trying to cultivate a new habit: dedicating at least half an hour to an hour each day to development.
Each day comes with its barrage of tasks and challenges, often leaving little room for respite.
Sometimes it's extra frustrating to keep things mulling in your head and not be able to act on it
When the focus is gone, progress is painfully slow
UUIDs are safer than using regular numeric IDs because they are not easy to spoof.
Since Strackt is a full SPA and API-driven application, passing data around needs to be extremely structured; enter the Data Transfer Object.
We don't stack cookies.
Two essentials and one optional. That's the whole stack.
No advertising. No ad networks. Privacy policy