In my experience, haters are some of the most passionate users, if you can do even the smallest thing to demonstrate a desire to improve, they'll often be huge advocates over the medium term.<p>I was working at a startup and we got some frustrating and hostile feedback from a user, I responded by acknowledging the issue and sending them a beta build that attempted to fix their issue. (it did not, but...)<p>Just reaching out and trying to engage made an enormous difference. They ended up contributing significantly to isolating and fixing that specific bug and others in the future, and referring us a few customers to boot, if I remember correctly.
I think an important thing to add is that users don't always know how to properly complain. So a difficulty is figuring out what they actually want. They're on the outside looking in, so don't know all the details but they can express that they have a problem. It can often be hard, and frustrating, to figure out what that problem actually is but if they're communicating then it is usually not too difficult to diffuse the situation. As long as they feel you are trying to understand.<p>Another part is that we're breeding a society of Karens. "The squeaky wheel gets the grease". The wheels not squeaking aren't getting regular maintenance or care. No one is incentivized to ask nicely but people are strongly being incentivized to scream. To generalize outside software: a loyal customer gets standard service but Karen gets a discount or something free just to make her go away. It's natural that we do that but it's the wrong reward system. When you reward a dog when they stop barking they only learn to bark.
You've not met a real hater if you think this, and should consider yourself very lucky. That was just a frustrated user.<p>A real hater will obsessively use your product, yet simultaneously attempt to find any reason whatsoever to hate your product (or you), no matter how small, and be extremely vocal about it, to the point of founding new communities centered on complaining about you. Should you address the issue, they will silently drop that one from their regularly posted complaints and find or invent a new one. Any communication you send to them will be purposefully misinterpreted and combined with half truths and turned against you.<p>Some of these people probably have genuine mental illnesses that makes them act like this.
Just to be clear, this particular user didn't ever become a fountain of sweetness and light - they were pretty touchy and cranky at the best of times, if I remember right (it's been over a decade), but accepting them as they were let them become a contributor instead of toxic.<p>Honestly I have thick enough skin that I'm happy to let them be themselves as long as we can reach a basis of professionalism and get a positive result.<p>You're right that there are many people you can't reach, and trying is a waste of effort, but I think an appreciation for human dignity requires me to at least make the attempt, and sometimes you're rewarded.
Yeah, which is why I think it's important to draw a line between a frustrated user (has genuine issues with his use of the product, can be turned by fixing them), a casual troll (reposts some bad feedback because he thinks it's funny) and a hater (malicious, bad faith, communication not recommended)
With my old saas app (now sold, and then the new owner killed it) I used to love getting angry emails. Almost every time the user ended up turning into an advocate and product champion. I don't know if they were "haters" per-se but they were almost always suprised to get an email back from a real person who cared about their concerns, and over time they changed their opinion. That may just be an artifact of early saas in 2010. Not sure if the same thing can happen these days.
Indeed. If someone hates your product, at least they care. Indifference is much harder to work with. My experience of dealing with haters:<p><a href="https://successfulsoftware.net/2024/02/25/it-might-be-a-good-thing-if-someone-hates-your-product/" rel="nofollow">https://successfulsoftware.net/2024/02/25/it-might-be-a-good...</a>
Agreed, I’ve experienced that myself. But I’ve also experienced the opposite: the user who always complains, doesn’t think things through, refuses to consider how their ideas would impact other users, doesn’t follow instructions…<p>In some cases, had I had the power to do so, there are a few users who I’d gladly have “fired”: offer a full refund in exchange for no more support.
People hate because they care. There's some exceptions (like bandwagon hating), but the people who hate on something the most tend to be people who <i>want</i> to like the product.
Exactly, they bought into the promise but the product didn't deliver. If a user expects your product to suck, you won't surprise (anger) them by being sucky.
Yes, it's often more frustrating to see a product with high potential fall flat than a shitty product be shitty.
Thats because most complainers really need their egos soothed more than anything.
You’ll also great some of the greatest feedback from them too.
Haters can be like bombs. You want to defuse them. Don't shake 'em. Don't drop 'em. Just render them safe. It's possible there's some gold in the ore; there might be, and if there is, accept it gratefully; but it's often hard to tell the constructive true-believer from the vindictive maniac. Your #1 job is to make it all inert, and to be able to walk away without an explosion destroying the business, social-media explosion or otherwise.
Don't fix what's making you bundles of cash :-D
Even the CEO's "apology" is pretty bad. He still finds a way to take shots at the original poster saying his original message was inflammatory (could also be read as how I'm justified in my response), that "he started it" and that the team was "spoken down to or treated dismissively" which they weren't. All the original feedback was about the project and was not directed at specific individuals.
His 'apologish' is basically the same as his original flamepost, but dressed in PR.<p>He places all blame on the user, basically calling him a dick again, and re-brags about their thousands of users, while attempting to sound noble.
The part about his team is so obviously performative, as though he’s such a great leader he just couldn’t help himself from being a dick because someone was “speaking down to his team”<p>A mediocre PR staffer got paid a decent piece of money to find a way to frame ab outburst as heroic
Harjot's initial feedback reminds me of one of my pet peeves:<p>If I reach out and say "I love that your product does X & Y, but it would be helpful if it also did Z", please don't reply with "Nobody needs Z."<p>Tell me you will look into it, or it's out of scope, or hard to implement, or literally anything other than calling me a nobody.
<p><pre><code> We have more users than everyone you just mentioned (combined).
</code></pre>
That's my favorite part. When an organization dominates a market, it's possible that they're so much better than the competition that the market has full-force chosen them, but that's almost never the case. Usually, it's because they've managed to avoid an open market all-together, (e.g. through exploiting intelectual property protection, byzantine compliance requirements, exclusive contracts made without concern for end users, etc…) and there's no need to make the product good, making it far worse than all of the competition (combined).
If someone sends you a nasty email, write a smartarse reply. Then delete it. No good ever comes from sending smartarse replies.
“Claude gets it”<p>No. It does not. It does not understand anything. Stop anthropomorphizing bots!
<i>Stop anthropomorphizing bots!</i><p>They hate that.
"Claude has been trained to handle this the right way"
How do you know whether a human brain understands something?
thank you for providing evidence that some do not.
Probably the same way that I can be assured your interpretation of red is mine.
Colors and color names are culture dependent, and you are not guaranteed that people in different cultures agree on what color something is.<p>The most famous of these discrepancies is Japan and green vs blue, or why does Jenkins by default use red, yellow and blue instead of red, yellow and green.<p>So I would urge using something other than colors as an example of shared human experience.
You're talking about culture and names, I am not. We all live in an objective reality where a red spectrum of light exists and we can differentiate among other colors.<p>This is the contention with the person I am replying to, they're acting as if objective reality doesn't exist. Humans can think, LLMs cannot.<p>If you can't admit to this there's nothing else worth discussing, but please don't mind my hands covering my wallet as I slowly back out of the room.
Some people are colorblind. Some people have more or less cones and rods. Our interpretation of colors is certainly not the same
You should steel-man the argument. GP is talking about qualia, obviously for the sake of the argument you assume the comparison is between two people with similar eyes.
The wild success of traffic lights disagrees with your statement.
The wild success of traffic lights is only wildly successful to those who aren't color blind. Do some reading.<p>Wikipedia: <a href="https://en.wikipedia.org/wiki/Color_blindness" rel="nofollow">https://en.wikipedia.org/wiki/Color_blindness</a><p>> <i>The colors of traffic lights can be difficult for red–green color-blind people. This difficulty includes distinguishing red/amber lights from sodium street lamps, distinguishing green lights (closer to cyan) from white lights, and distinguishing red from amber lights, especially when there are no positional clues (see image).</i><p>Publication from 1983: <a href="https://pmc.ncbi.nlm.nih.gov/articles/PMC1875309/" rel="nofollow">https://pmc.ncbi.nlm.nih.gov/articles/PMC1875309/</a><p>> <i>All but one admitted to difficulties with traffic signals, one admitted to a previously undeclared accident due to his colour blindness, and all but one offered suggestions for improving signal recognition. Nearly all reported confusion with street and signal lights, and confusion between the red and amber signals was common.</i>
The wild success of traffic lights comes from having 3 colors at fixed positions. You put those 3 colors in a single color changing light and I would assume the accident rate would measurably increase.
The fact that a single emitter traffic light that simply varies its color doesn't exist also disagrees with your statement.
Denial of an objective reality is a symptom shared by various strands of bad thinking our current era.<p>LLMs do not think. That's reality.
I love hearing stories from a people way senior my age and I love befriending them. Here is a story from one of the seniors I occasionally helped out with their tech/phone/internet. He was once stationed in a rural part of India to lead a team for a once-popular phone service provider. There was a local person who would barge into their office and complain a lot, arguing about the quality of the connections and the drops in areas around the town.<p>Eventually, he became the benchmark of their team’s work: “What would he say? We need to fix that. What were his complaints?”<p>He swears by this and has repeated the story a few times. One of the angriest customers becomes the benchmark for the team and the service. There are no bad customers; there are only passionate ones.
It's very hard to accept criticism; very hard. But OP's view is the mature, thoughtful way to go about it. Some people are going to be mad-as-hell, and they just will be. The analysis and advice is good. The initial response from the founder wasn't great and because we all like rooting for the underdog, there was a pile-on. Bad on us.<p>But, just to see how accepting criticism works, it wasn't Dostoevsky who had that quote about happy families, it was Tolstoy. :-)
I work in a big company where everyone knows how to "accept criticism". What they don't know is how to fix the problems. The company here had a tweetfest, then a blogfest, then an apology fest. Did they even consider sitting down with a glass and looking at the product?
The fake apology at the end makes this quite funny.
"I was just protecting the team". "I learned many lessons". Etc.
Good at marking this as a company to avoid.
Your harshest critics are often your most invested users. In this busy age, the people who take time to complain care, and those who don't just ignore. The opposite of love isn't hate, it's ignoring. Once you see criticism as engagement rather than attack, the right response becomes obvious.
Is this going to become a generational thing?<p>I feel like millenials are kind of programmed to think that the customer is always right (or at least that this is the only stance you should take).<p>Will some younger generations think that the world is better off without the people who think that screaming at people is OK as long as you are a customer?
warning: incoming generational stereotypes<p>The original phrase "The customer is always right" had an important caveat: "... in matters of taste". Somehow boomers managed to forget the caveat and created a culture of treating customer service workers like personal slaves and demanding to be treated like royalty. I don't know that Millenials think the customer is always right, but I do see that the Zs think anybody can be wrong, especially customers, and I love that about them.
Complaints are amazing! I've said for years that you know you're succeeding when people start complaining. Complaints are a sign that users see something potentially valuable, and are frustrated that they can't get there. Even if you can't prioritize the fixes that would be required, you should still embrace them.
I learned the first time I got slashdotted:<p>1. Don’t engage in public with an antagonistic or upset user or reviewer.<p>2. The thread will unroll itself, and the immaterial ones will die out on their own.
I think the most important rule is only write in public for the secondary audience, not the antagonistic user.<p>People watch what you say, sometimes there can be value in responding carefully if it plays well to spectators.
I often read reviews of places and things I'm even tangentially interested in. As a user, there's little more unprofessional to me than a company replying to negative reviews with anything but an apology, or offer to help or do better.<p>So many places, especially local ones, take every sub five star review as an insult and invitation to argue. I'm actually shocked by the percentage of places that do this. It drives away my business, and I can't be the only one.<p>Even not replying at all is a better strategy, IMO.
The issue here is that coderabbit is indeed a crappy product and then you have this problem that we want people to be nice to your products but sometimes it is just pity.<p>Personally I'm not a small indie dev but if asked, I would have the same feedback as Aiden about it.<p>First time I encountered it, it was with an open source project where it was mandatory I think and this agent pissing kilometers of useless crap at each interaction was really really annoying.<p>But looking at the CEO response, I think that the product might be at the image of its leadership: egocentric.<p>Like as an user it is just one of the tool like another one for you to use, you want it to be discreet, direct, providing you tldr and no more.<p>Instead, you get something that will try to get as much visibility and your attention as possible, taking all the space. Like if it was the main and only thing in your software forge.
Shorter: "Don't take it personally". Also, people tend to dial down their flamethrowers once they see that you're listening.
Good negative feedback is a public service, a gift from the critic to you, and a severely undersupplied one in this world we live in.
OP is wrong, ad hominem is the best way to both defend your intellectual integrity and also drive engagement
You are totally the kind of person who would believe something like that.
In fact, acknowledgement of any kind is failure - report the truth as anything counter to the feedback, and tell everyone how much support your counter argument has by quoting numbers no one can verify (important)
What a stupid opinion.
“There are only two kinds of languages: the ones people complain about and the ones nobody uses.”
― Bjarne Stroustrup
Microsoft Teams developers, please come @ me.
The underrated trick here is separating “signal” from “status game.” Even hostile reviews often contain one actionable invariant (“this workflow is brittle”, “pricing feels dishonest”), and the rest is just the reviewer performing for an audience. If you respond only to the invariant (and maybe ask one concrete follow-up), you de-escalate without rewarding the theatrics — and you also create a public artifact future users can trust.
> When someone says they hate your product<p>Listen.<p>Period.<p>Sure, you will inevitably run into people who are impossible to please. However, for the most part, the vast majority of the people who have a complaint are taking the time to attempt to communicate with you or your company about a need you failed to meet. This can be something that's broken, not implemented or done badly. In all cases, they are motivated by wanting to fix the problem for themselves...which is likely to fix it for lots of others who might not be as vocal.
Before this I hated code rabbit, sick of hearing them on podcast ads.
Frustration is the fuel for innovation.
Interesting thought! In moments like these, capturing the innovation can be ignited by asking whether the comment was frustration or feedback, or said slightly differently “was that trying to be helpful or hurtful?”. Tends to get the other party to rethink their words and produce a more productive dialogue. It’s a tool we can all use both at and outside of work :)
every product will have haters. to attack the poster personally and then double down with a non-apology kinda shows how clueless their leadership is
Most know some version of the 4 types of customer in marketing, but only a few figure out 3/4 classes of sales are not worth the effort.<p>1. The miser: No matter the cost, the right retail price is $0. These folks make up 82% of the market, but are usually effectively irrelevant in terms of revenue. Yet if you sell low-end low-margin products, than these are your customers.<p>2. The technical: Give them a list of specifications, and leave them alone. These people already know what you have for sale, and probably know the product better than most of your team. Too bad, these folks are <3% of the market, and while they have opinions they also don't matter in terms of revenue.<p>3. The sadist: These people are only interested in making people miserable, and for whatever reason are always a liability to have around even in the rare event they buy something. At <5% of the market they are also irrelevant in terms of revenue, but will incur additional losses though nasty cons etc. Your best bet is to give them free swag bribes, and refer them to a competitor because they are so awesome.<p>4. The emotional: These people are the highest profit market, as they are more concerned with how they feel about a product or brand. They don't care much about hardware performance specifications, but rather focus on the use-case in a social context.<p>One may disagree, but study 23000 users buying habits... the same pattern emerges for just about every product or service. Note, these classes are only weakly correlated with income level.<p>Thus, depending on the business it is absolutely possible to ignore the vast majority of the market while still making the same or greater profit. Yet if a product is mostly BS, than the online communities will figure that out sooner or later. =3
Meh, CEOs response was bad, but I hate people with a burning passion when they express feelings like that about a product. Just stop using it and walk away and stop making it harder for other people to live. If you want to offer feedback then lead with that.
We tried it CodeRabbit. They enable beta features without asking, so one day your GitHub issues get AI responses without anyone ever asking it to respond to it. I think the criticism was warranted. I think it is OK to let people be passionate about the tools they have to use. Ultimately, we decided to disable CodeRabbit. But there were definitely some people on our team that felt like they were forced into using it.
> Just stop using it<p>Unfortunately, not always an option without making major lifestyle decisions (for example, software required by a job)
Can't stop, they force us to use it <a href="https://ifuckinghatejira.com/" rel="nofollow">https://ifuckinghatejira.com/</a>
Not every consumer of a service like CodeRabbit will be in a position to make decisions about the tools their org adopts, or even be involved in the relationship with the vendor. Are they not entitled to express exasperation in a public forum?<p>The guy offered some pretty valuable feedback to help improve the product. Business idiots with ego problems can bury their head in the sand at their own peril.
> but I hate people with a burning passion when they express feelings like that about a product.<p>Interesting choice of words.
I find the things I hate the most are the things that I want to like. What I hate specifically is the disappointment of seeing ‘bad’ when I expect ‘better’
[dead]
Read your article.<p>It’s interesting how quickly criticism cools when ownership is taken instead of resisted<p>Thanks for sharing.