> In fact, a reliable engineer ought to be comfortable working on products people hate, because engineers work for the company, not for users.

I prefer to take pride in my work. This sounds like hiding ones neck to collect a paycheck.

I prefer to have hard discussions about pivoting or making changes so that we can improve the product, or company, for our users. Anything less is simply "not doing the job", or at least making a serious consession, in my opinion.

I don’t know. I agree with the point that indifference is worse than hate but I would not take a lot of this article’s advice.

I’ve spent my career finding and working on things people love. I’d join a less stable company to know I’m actually putting products out that are worth spending time on.

This article comes across as coping to me, “it’s okay to ship junk, just comfort your tears by rolling in your pile of money.”

There are different kinds of hated products. Some are hated because they have bugs. Some are hated because nobody wants to use them at all. And some products are entirely a net negative for the world.

The problem with the article starts with wording. If I hate a piece of software then almost by definition it has failed to do its job well as I believe software's job is to help me do something. But I usually don't hate and with age I even accept and appreciate that there are trade-offs to be made.

The problem is.. that software today seems that the trade-offs made are akin to "will use accept invasive pattern A or invasive pattern B". That is not a technical real trade-off. It is not structure c vs structure d. Rather, it is an intentional making world a worse place to live in.

And I still don't hate it.. I hate the people who make it.

> The worst products are not hated, they are simply ignored

False. Ignored product are not used by anyone thus they don't demand any love or hate at all.

The worst products are those into which users are forced against their will. Things like KYC providers are the stuff that everybody has to use and everybody hates.

> working on an ignored product is much worse

False. Working on an ignored product can be extremely cozy because nothing happens except the paycheck.

There is a kernel of truth here: programs like CMake, Wordpress, or Electron get insane volumes of hate because they tackle extremely hard, extremely valuable problems half-assedly in a field of competition where no one else manages even a quarter of an ass. The hate stems from usage * not being that good, the usage stems from being the best.

I do worry that applying this heuristic at microsoft is unwise, because microsoft is so famously good at getting people to use software against their will- if usage decouples from being the best, then the hate becomes shoved-down-throat-factor * not being that good, which is a very different place to stand and declare onesself to be helping.

I work on a platform that a lot of customers "hate", or at least get frustrating experiences from. With many vocal on reddit, or in the reviews.

As software engineers, we are nowadays actually expected to handle customer service escalations (ie: when customer service cannot resolve a given situation, and the client is persistent enough, or borderline threatens legal action).

Strangely, I found dealing with those these customer escalations some of the most rewarding work. It feels very real as I read the long winded customer support ticket, feeling the user frustration, and finding the root cause and resolving the issue, or at least being able to understand and explain. Afterwards, internally trying and pushing for changes that would prevent the frustrations and escalations is also very rewarding.

I found this more rewarding than some other initiatives we have internally as they sometimes feel less connected to actual problems that are happening and that nearly everyone ignores.

The user/company misalignment described here feels like a symptom of scale more than an inherent truth about software work. In small or niche software—a team of two serving a few hundred operators, say—you simply can't afford to build something your users hate, because there's no insulating layer of sales cycles, contracts, or switching costs. The feedback loop is too direct. The article seems like genuinely useful guidance for navigating a large org, but it's describing a very specific structural condition rather than software engineering in general.

Sean, I wonder why people are so negative here. I think they’ve never worked in big tech.

As a staff swe in big tech your blog posts resonate strongly and reflect my own experience. But I can see if I didn’t have that experience I’d be unable to relate or even understand.

Maybe it is nihilism - but I think that’s also a natural result of working for big corps.

The nature of feedback is that the most vocal express their dislike of a product more loudly and are noticed. The people who like the product won't often take time to express it. So it would certainly help you to take the criticism with some salt.

I spent a couple of years of my career working on a multiplayer / social game. We definitely got some angry feedback on that, but overwhelmingly the users loved it. Our game hovered around a 92% approval rating. I even got fan art! I think I’ll always look on that period as an absolute highlight of my career. I shifted industries to renewable energy driven by a personal mission to work on a greater cause. It’s B2B so I’m back in the familiar place of having users who I imagine would rather be doing something else than using our product. If my work means they get to spend less time at their computers then I’m happy.

Don't attach your pride to how well a product you work on is received. You can still take pride in improving a poorly received product, or even in just trying.

> Some beloved features have very shaky engineering indeed, and many features that failed miserably were built like cathedrals on the inside.

What's under the hood, the people who use the product, don't care.

Customers, and ultimately companies as well, only care that the product works, is maintainable over the long term, and is bug-free.

Cathedrals in the desert are useless, and over-engineering only complicates things when there's no need yet.

I've also seen several successful projects that were actually quite weak behind the scenes, but they were simple and functional.

Most software is just there to get the job done. I’m building compliance tools that most users would very much like to never use as they’re just adding overheard over what they consider real work. You can still strive to make the software in a way that makes the unpleasant task of having to use it as painless as possible.

I mean, I once turned down a really interesting realtime data processing project because it turned out it was for the military's warships, and I'm pretty sure its target market would've hated the product.

But maybe that's just me.

The most successful businesses are often the most harmful forces in society. There's a lesson there.

I like GitHub Copilot, it's pretty okay!

Now, whoever worked on Oracle DB or Oracle Forms, or Oracle ADF, now those are some products I hate for a variety of reasons!

“Almost every engineer will work on a product people hate.”

No. Forcing people to use a product they hate is privilege. It’s about power. Monopolists like Microsoft and Google can do it, companies that face market competition can’t.

All of this guy’s takes are so funny to me. He’s clearly been forged in the fire of utterly cursed and corrupt companies like Amazon, and it bleeds into his entire world view. He can’t even conceive of the idea of actually wanting to create a good product, it’s all seen through the lens of promotions and self-furtherment.

In a perfect society, companies would find that the more negative externality they create, the more difficult a time they'll have finding people willing to do it for them. One case in point is when a civil-oriented software company starts taking on military contracts and putting their people to work towards death and destruction. In a perfect society, the reaction we would get is the employees going "wait a second; I liked this company when I joined, but I never signed up for this." … and even in our less-than-perfect society, we do get some of this; what we need is more of this, not less.

> engineers work for the company, not for users

Honestly I don't see a big difference between that sentiment and "I was just following orders".

That kind of mindset eventually leads to situations like yesterday's headline about the Artemis astronauts finding out that their computer inexplicably runs two instances of Outlook which both do not work [0].

Situations like Windows updates causing data loss by updating and rebooting without the user's consent.

Or situations like one year ago when I had to help an elderly person after MS suddenly replaced the easy to use Mail app with an enshittified one that wasn't just much more complicated, but also had an untranslated English interface because MS couldn't be bothered to translate it before forcing it onto users worldwide.

[0] https://news.ycombinator.com/item?id=47615490

I had an epiphany about the software industry when I stayed at my parent's place and used a microwave that had the worse UX of any machine I had ever seen. Basically there was no start button, there was no way to increment the timer after you started, there was no '10 second or 1 minute preset' like every other brand and the only way I could figure out to make it 'work' would turn on a super loud fan which would keep running even after the Microwave had been stopped; I had to pull the plug on the thing to make it stop.

It was a popular brand and I suspect it probably sold well. The mind-boggling dysfunction may not have been obvious at a glance when the consumer made the purchasing decision. The UX was so bad, I still have nightmares about it.

As I was trying to use the damn thing as a user and kept running into one hurdle after another, it triggered a flashback of my experience of debugging complex software as a software engineer and I thought to myself "F***, I chose the wrong career. I'm cooked. The user doesn't care. The user doesn't care AT ALL." In that moment, I understood that getting replaced by AI was the least of my problems. Far bigger problems had been there since the beginning. I just didn't notice them.

I just thought about the software engineer who had to implement this retarded UX... I imagine they would put on their resume "Wrote the firmware for <popular electronics company>" and it would sound really good. The worst part is that it's probably not even their fault that their work sucks.

Anyway it just made me realize how unmeritocratic this industry is. We could do a great job or a horrible job and most of the time it has nothing to do with career progression and opportunities.

Companies don't want to delight their users! They simply want to take their money!

IDK why these vacuous corpo tropes appear on the front page of HN every now and then. Sounds like exactly what a quasi-technical, management-leaning staff engineer would say.

Sure, in the end we work for these faceless, meat-grinding machines. But more or less, we all have some semblance of autonomy, and I absolutely can choose not to work on a product that people hate. I can switch teams before switching companies.

To some extent, I also just do what leadership asks, keep my mouth shut, and collect paychecks. But whenever that happens, I don’t gaslight myself by writing a post on why it's supposed to be this way.

To me, this seems like someone who is married to their paycheck and would do whatever necessary to protect that.

Are people really using Github CoPilot on their own volition or is it just "my employer only lets me use this tool"?

Finding value in giving up one’s values.

Author mentions working on product people hate, GitHub Copilot. Honestly it ain’t too bad. Definitely better than a lot of “enterprise” software.

I worked a lot of food service jobs when I was younger, and as much as those jobs can suck, one big thing that is nice is delighting customers.

Assuming of course that you aren’t working at Slop Burgers, but even then… almost everyone is happy to get an ice cream cone, or a hamburger with fries, or just food in general.

It’s a shame that white collar professions typically have such a distance between make thing and give it to customer, who’s excited to receive it.

I work on a product that is so loved and hated at the same time. With some people it’s almost set off its own subculture, and they will roll with nostalgia if they ever used it.

On the other hand some other people will claim it’s the hallmark of enshittification, overchurned with features and a sinking mess.

I agree with both. It’s a strange situation and very difficult to move the needle towards more love at this point

People talk a lot, but their wallet really speaks. I don't build for people's mouths. I build for their wallets. I'm happy with outcome.

Pure cope.

It is extremely possible to work on a product people don’t hate, and still maintain a realistic perspective on your engineering abilities or impact or whatever.

If you’re toiling on a product that’s actively making the world worse, quit now. There are better gigs out there.

Seans quest continues gaslighting himself one blog post at a time. As usual on his pieces away from pure technology I have the opposite opinion.

Do you want to know what God thinks about money? Look around and see who he gives it to.

[dead]

[dead]