Is it profitable to be a programmer who "bugs" new features?

Question

Career in IT

In my experience of working in medium and large companies, I noticed that programmers differ quite a lot in what tasks they can solve.
Some do some complex infrastructure tasks, do it slowly, thoughtfully and with such a global approach.
And others somehow mindlessly figure out new functionality of medium quality with a certain pool of bugs and inconsistencies. But they do a lot of things right. You open the chart for a quarter, some conditionally made 7-10, and the second about 50.
In theory, it seems that the former should be valued higher and receive more, but in practice I saw that due to the fact that products were cited for new features, such programmers constantly looted some bonuses, buns and promotions.
Is this the case in other companies, and would it be beneficial for a programmer who closes tasks with "average quality" code?

Answer 1

A programmer usually sits in the place of a team leader, who works just "thoughtfully and with such a global approach", and all tasks go through his review. It just won't let through the code that was put together in a quick way. Moreover, it will lower the quarterly estimate, in the case of regular jambs.

Answer 2

It purely depends on the task we have, and they both get the same, everyone sculpts the code through a joint review, even sometimes I look at their code that you they scored points for approval