Thank you. Finished top 2 on a Sunday and now I know what to build next.
247 upvotes, 34 comments, finished second on a Sunday. The July launch got 362 and finished third. Better rank, smaller day. Both true.
The comments were worth more than the votes. A few things I didn't have good answers for, which is more useful than an upvote.
Out-of-order webhook replay isn't deterministic yet. Seven people across two launches have asked. That's what I'm building next.
Someone described a test fixture that had encoded a buggy assumption. It was defending the bug and would have gone red the day the fix shipped. A whole class I hadn't thought about: fixes that only work for people who arrive after them.
Someone asked about partial writes. Partial webhook delivery, yes. Partial writes, no. That's a real gap.
One mistake you can avoid: I set this up as a new product instead of a new launch under the existing one. Started with 3 followers instead of 709. Support moved it before the day was out. It's a dropdown. Check it.
If you've hit that test fixture problem before, curious how you handled it. Roadmap for the next few weeks is entirely things people said in these two threads.
Replies
The follower point is the one I'd flag loudest for anyone reading this later. ComplaintForge only has one launch so I can't compare rank movement the way you can, but the number that stuck with me from launch day was not the 12 points, it was that every one of the 15 comments came from someone I'd actually replied to within minutes, not the vote count. Sounds like your 247 has the same shape, votes lag, comments are the actual signal.
On the test fixture defending a bug: I've hit a version of that in a smaller form, a test that asserted against a wrong value because the wrong value was what the code had always produced, so the test passed by matching the bug rather than checking the behaviour. The fix that held for me was writing the assertion from the spec before looking at what the code currently did, not after. Doesn't scale to catching it automatically, but it stopped it happening again in that file.
Softorino 💻📲
Congrats Raj, second on a Sunday is a strong close. I like that your biggest takeaway is a roadmap item, seven people asking for deterministic replay is about as clear as customer signal gets. Well earned.