[possibly_not]

>The developers MUST care for the quality, not outsource it to some external team. The desire of large corps to spend huge amount of $$$ to create artificial roles to water down ownership can never cease to astonish me.

As a former quality-focused dev, I can tell you that the industry beats it out of you with a club. There is always somebody above you who cares only about their own career ambitions and has more leverage than you do. This leads to a horde of devs who just do what they're told and not much else.

Businesses are all about risk management. The safest way to de-risk a business is to water down ownership, at the cost of injuring quality-focused devs. You're only a cog. You need to only be a cog to them. They must to be able to replace you with another cog when you leave for greener pastures.

[andrekandre]

  > I can tell you that the industry beats it out of you with a club.

yep, i can say i've seen this over and over; more than anything incentives are for the next okr or whatever to be completed so they can move on to the next one asap.

i've seen pr's sent out for review that literally didn't work or crashed immediately on use... as if the expectation is qa will report whatever needs fixing but thats fine cause its "in qa now" so development is "done".

[baq]

That’s just Goodhart’s law.

"When a measure becomes a target, it ceases to be a good measure".

[pdimitar]

I don't disagree with you, I've seen the same (a lot) but you can still go to another company that prioritizes quality a little more.

Definitely can take a while to find one though, that much is true.