[cletus]

A lot of the time, a lack of bugfixes comes from the incentive structure management has created. Specifically, you rarely get rewarded for fixing things. You get rewarded for shipping new things. In effect, you're punished for fixing things because that's time you're not shipping new things.

Ownership is another one. For example, product teams who are responsible for shipping new things but support for existing things get increasingly pushed onto support teams. This is really a consequence of the same incentive structure.

This is partially why I don't think that all subscription software is bad. The Adobe end of the spectrum is bad. The Jetbrains end is good. There is value in creating good, reliable software. If your only source of revenue is new sales then bugs are even less of a priority until it's so bad it makes your software virtually unusuable. And usually it took a long while to get there with many ignored warnings.

[conradfr]

Jetbrains still likes to gaslight you and say you are wrong about bugs or features.

Recent example the removal of the commit modal.

[switch007]

The whole New UI debacle really set the tone and expectations and I don't see them changing. They seem like a different company these days? Maybe I didn't really notice in the past.

[kg]

The jetbrains model is every new release fixes that one critical bug that's killing you, and adds 2 new critical bugs that will drive you mad. I eventually got fed up and jumped off that train.

[hanikesn]

What when is this going to be finally removed? I'm still reverting back to the old dialog on every machine.

[hulitu]

> Jetbrains still likes to gaslight you and say you are wrong about bugs or features.

They learned from the best: Microsoft.

Microsoft cannot fix bugs because it's "engineers" are busy rounding corners in UI elements.

[tjoff]

... but support for existing things get increasingly pushed onto support teams.

And support teams don't fix bugs?

[Ygg2]

You're removing autonomy from the support team, this will demoralize them.

The issue becomes, you have two teams, one moving fast, adding new features, often nonsensical to the support team, and the second one cleaning up afterward. Being in clean-up crew ain't fun at all.

This builds up resentment, i.e. "Why are they doing this?".

EDIT: If you make it so support team approval is necessary for feature team, you'll remove autonomy from feature team, causing resentment in their ranks (i.e. "Why are they slowing us down? We need this to hit our KPIs!").

[zombot]

The grammar of your own comment isn't any better.