But I decided to leave it because I think I stand by the implication that reputation for specific technical blogs can be earned or used up. Fly.io has earned a lot of reputation and I (and I guess others) clicked on a title I would not usually have because I saw the domain. In this case I feel like some reputation was "used up" and I am (slightly) less likely to click on a post solely because I see a fly.io domain in future.
Maybe I am just not the target audience for the post and it is better than my assessment, but if not then I think people value HN as an honest audience that doesn't hold back on criticism (I know I do and I have received harsh but valid criticism from hn on stuff I have written).
Fly.io can probably keep making front page based on reputation if there is a balance of very high quality content and other posts, but I feel like something like this could have been 1000% better with another revision round and some editing (probably only 20% more effort) so I will keep saying stuff like this I guess?
Don't. I can honestly say that I didn't write this post targeting HN. I'll go further... this post wasn't meant for people who are unlikely to use https://github.com/fly-apps/dockerfile-rails#overview. I recently added some features to that gem whose usage may not be intuitively obvious. I wrote this post to explain some of the motivation for those features.
I don't know how to mark posts as not intended for HN (and truth be told, if there was such a feature, I'd be inclined to overuse it). I don't know where else I should have posted this content, but I'm not sure I would be inclined to move it. In any case, this post, as written, serves a purpose for me. Somebody not you and not me felt it belonged here. We can both second guess that decision. Either way, there is no reason for either of us to feel bad.
I love fly.io and appreciate the content but that doesn't sit right with me.
I just worry about us writing less stuff because people assume there's going to be some stunt driving sequence or shootout or CGI or whatever, and not everything people write here is like that.
Minute later
(I may be getting pushed into responding adversarially here just by message board dynamics. Sorry. Like I said up front: it's a weird thing to write! But what am I going to do, filter my thoughts before writing them on HN?)
> But the only sane response we can have to do that is: we just write what we want to write, and we let the community do what it's going to do.
Move over paxos and sqlite3; HN needs FlyLLM and Fly vGPU to satiate its appetite now ;)
Can I ask you not to say things like this? Specifically: this idea that there's a bar for technical stunt driving that we need to clear to get things up on the blog. I know I can't demand that of anybody; I'm just asking.
I can't tell you how many things we haven't written on our main blog because we're worried about whether it's as technically interesting as the "Gossip Glomers" thing we did with Aphyr.
Sam's a good writer and this is a pragmatic post about an approach he took to building something. The world is incrementally better with this post in it than without it. Holding off until we could have integrated LiteFS and written a 4 paragraph coda about sqlite3 internals would not make the world a better place.
I worry all the time about "Fly.io fatigue" on HN, for what it's worth! But the only sane response we can have to do that is: we just write what we want to write, and we let the community do what it's going to do. If 'dang gave us a header we could use to dampen some of our posts, we'd use it. :)
If I'm crazy to ask this, say so. We've been grappling with this for years now; if we knew exactly how to handle it, I wouldn't have to write weird things like this.