The roast continues. 💀
A few days ago a stranger roasted my debug logs. I fixed it in 1.5 hours and felt pretty good about myself.
Then someone reviewed my API routes and said: no structured output, no context in logs, login failures not mapped to domain exceptions, no global error filter, unsafe catch blocks...
Checked. Almost everything was right.
So today I spent the morning fixing 4 products:
ChangelogHQ / FeedbackBox / MailTrace / TestimonialWall
80+ routes. Fully standardized.
Thanks for the free code review, stranger. Again. 🙏
I used to think 'it works' was enough.
Apparently production-grade is a moving target.
Every roast is a free audit. Keep them coming.
Screenshot: A Chinese developer on Xiaohongshu reviewed my code and listed every logging issue. Almost all correct.
#buildinpublic #indiehacker #nodejs #saas
How do you get users to review your infrastructure for free? Only using build in public posts on social medias?
Honestly, I didn't plan it — it just happened naturally through build in public.
I share real work: actual grep outputs, real error logs, honest mistakes. Not polished updates.
When people see the raw stuff, some of them can't help but respond — especially developers who spot something they'd fix differently.
The key is specificity. "I'm struggling with X" gets silence. "Here's my actual code/output and here's what I tried" gets engineers in the comments.
So no special strategy — just share the real mess, and the right people show up. 😄