I wanted feedback on SailWP. Honest, unfiltered feedback from people who know WordPress inside out. So I did what any reasonable person would do: I posted it on r/WordPress.
What I got was a masterclass in internet survival.
Post One: The Ambush
My first post (aff) had a title that, in hindsight, was basically throwing a lit match into a room full of gasoline:
“WordPress is broken. The core team won't fix it. So I did.”
I came in hot. Strong opinions about the state of WordPress. The leadership vacuum. The absurdity that in2026, you still need five plugins to do anything useful with a fresh install. I believed every word of it. I still do.And I wouldn't change a single word.
The post got downvoted hard.
Some of the criticism was completely fair. The landing page was in Dutch only – not ideal for an English-speaking subreddit. I had an email gate on the download. I hadn't documented plugin compatibility. Thosewere genuine blind spots, and the commenters who pointed them out were doing me a favor.
But mixed in with the helpful stuff was a different kind of feedback. Philosophical objections dressed up astechnical criticism. “This should be a plugin, not a theme.” “Put it on GitHub or it doesn't count.” People whoclearly hadn't tried the product telling me it couldn't possibly work. And then the personal attacks, which wereremarkably creative for people who supposedly didn't care about my project.
The frustrating part? Some of the genuinely positive and helpful comments got downvoted into oblivion.Reddit has this beautiful mechanism where a handful of early downvotes can bury good feedback beforeanyone else sees it.
What I Actually Fixed
Here's the thing about getting roasted: if you can separate the signal from the noise, it's incredibly valuable.
Within 24 hours I had:
- Built an English landing page at sailwp.com
- Removed the email gate — one click download, no account needed
- Tested and confirmed compatibility with a bunch major plugins
These weren't small tweaks. The English landing page alone opened up SailWP to an audience I'd beenaccidentally excluding. That feedback was gold, and it came from people who took the time to actually look atwhat I'd built.
Post Two: The Comeback
The second post (aff) took a different approach. I acknowledged getting burned. Cheekily. Addressed the criticismpoint by point – what I'd fixed, and what I wasn't changing and why.
It shot to number one on the subreddit.
The upvote ratio started around 85%. Real conversations were happening. People were engaging with theactual product instead of arguing about philosophy. For a few hours, it felt like exactly what I'd hoped forwhen I first posted.
Then the haters found it.
The Low Point
By the end of that day, some comments were getting under my skin. Not the technical disagreements — I canhandle those all day. It was the unfounded accusations about my character. People who hadn't read the posttelling me what I'd said. Confidently wrong statements presented as facts. The sheer unwillingness to engagewith anything I'd actually written.
I updated the post. Said I was done with Reddit. Didn't need this kind of thing in my life. I have a good life.Let the haters be angry at someone else, somewhere else. Why would I voluntarily subject myself toanonymous strangers who seem genuinely angry that I built something?
I meant it when I wrote it.
The Morning After
After a night's sleep, things looked different.
I went back and actually looked at the numbers. My post had been a massive hit. Way more positiveengagement than negative. My DMs were full of thoughtful messages from people who'd tried SailWP, hadquestions, wanted to help. Several people had sent genuinely useful technical insights that I implemented intothe theme that same week.
The loud minority had been exactly that – a minority. They just happened to be very, very loud.
The Teenage Gamer Awakens
Here's something about me that's relevant to this story.
In my adult years I've mostly stayed away from online forums and social media debates. But in my teenageyears? I was forged in the flames of online video game forums. Absolute scorched earth, take-no-prisoners,argue-about-everything-until-3am forums. I am not someone who lets himself get run over. By anyone. Letalone anonymous trolls on Reddit.
So something clicked.
I know this game. I've played it before. I'm actually good at it.
I started responding to everything. Every comment. Every criticism. Every snide remark. Politely, factually,but firmly. It turned into a game of whack-a-mole – except the moles had absolutely no idea what they weretalking about, which made it surprisingly easy. And fun.
The third post (aff) was about architecture and a demo video. By that point I'd found my rhythm. Engage withsubstance, deflect the nonsense, and let the product speak for itself.
What I Learned
Building in public is powerful. I'd never done it before. SailWP was a solo project, built quietly at mydesk for months. Putting it in front of a hostile audience forced me to articulate things I'd never had toexplain. Why this architecture? Why not GitHub? Why a theme instead of a plugin? Having to defend thosedecisions made them sharper. Some of them changed. The ones that survived are stronger for it.
Separate signal from noise. Not all feedback is equal. “Your landing page is in Dutch” is actionable. “Youshould put it on GitHub or I don't trust it” is a preference masquerading as a requirement. Learning to tell thedifference quickly is a skill, and Reddit is an intensive training ground.
Know when critics have a point and when they're projecting. Some people genuinely disagreed withmy approach for good reasons. I respect them, even when I still disagree. Others were clearly working throughtheir own frustrations about WordPress, about open source, about whatever – and I just happened to bestanding in the blast radius. Those are two very different things, and responding to them the same way is amistake.
Community is worth the chaos. For all the trolls and drive-by downvotes, I got something I couldn't havegotten any other way: real feedback from real users who actually know WordPress. The DMs alone were worthevery negative comment. Several of those conversations are turning into ongoing relationships. One hostilesubreddit gave me more useful product direction than months of building in isolation.
Would I Do It Again?
In a heartbeat!
Not because it was pleasant – parts of it genuinely weren't. But because the alternative is building in a vacuumand hoping you got it right. The Reddit experience compressed months of learning into a few intense days. The product is better for it. My skin is thicker for it. And I now have a network of people who've beenfollowing the journey from the start.
If you're building something and you're nervous about sharing it publicly: do it anyway. Post it on Reddit. Let them roast you. Read every comment. Fix what deserves fixing. Stand your ground on the rest. And maybe keep a healthy sense of humor about the whole thing.
The internet is brutal. But it's also, occasionally, exactly what you need.
