Making time isn't the problem; I make the time. Every so often I clear an afternoon to tell people about strackt, open the list of people I've been meaning to write to, and actually start. Then something pulls me sideways: a fix I spot halfway through the first line, an idea for a feature, an email that needs an answer. Anything, really, as long as it gets me out of the thing I sat down to do.
Because that thing is pretty hard. Telling someone about something you built, and then asking them to try it, feels a lot like boasting to me, and every one of those distractions is a perfectly good reason not to.
The weird part is that this is my job. I've done it for bigger companies for a long time, I know how it works, and still I can't do it for myself.
I've got reasons, of course.
I don't want to boast. strackt is the thing I'm proudest of having built, and that's exactly what makes it awkward; saying out loud that it's good sounds like talking myself up.
I don't want too many people at once, either. I've said that before as a principle, and it is one; it's also quite convenient, because a small group doesn't take many messages to keep going.
And I don't want just anybody's feedback. I want it from people who know what they're talking about, who've run servers and been woken up by them, so I go one at a time: a message, a conversation, a server of theirs on strackt and a list of what they ran into. That part works. It's slow, and it's the best feedback I've had.
The trouble is what comes after. Every one of those conversations teaches me something, and everything I learn I want to go and fix: a step in onboarding, a sentence on the website, the way a restore explains what it's doing. So the conversation turns into a Linear issue, the issue turns into an afternoon, and the afternoon I'd set aside for the next conversation is gone...
I'd defend any one of those reasons, right up until I put them next to each other. Together they make a comfortable wall, and lately I've been leaning on it.
There was a fourth reason, and it was the best one: the story wasn't ready. The line itself has been there for a while:
You bring your code, you bring your servers. The rest is our problem.
What wasn't there was what "the rest" means. Most tools in this space lead with the deploy; strackt is mostly about what comes after it, the patches, the upgrades, and checking that a server you own stays the way it should. It took me until October to put that first, and now that the website does, there's no part of it left I can call not ready.
And it's starting to hurt. I've written to twelve people in seven weeks, the seven weeks I'd said were for outreach; and the one thing that reliably makes strackt better is exactly those conversations. I can't just accept that. So the next message goes out before I open Linear.