DEV Community

Discussion on: Is it good or bad practice to make developers pay money for his bugs?

Collapse
 
pchinery profile image
Philip

I have not heard of that myself and find probably somewhere between doubtful and utterly wrong.

If very small amounts of money are collected (i.e. 1-2€) and they are used to buy pizza, beer or cake for a release, I would still find this approach doubtful, but could see a point to sharpen the view of everyone to good code and in the end it's used to have a small release party.

But as you wrote, this can distract from fixing the issue to either hiding mistakes or arguing if this should be accounted for. This is not very helpful for code quality, team morale or pretty much any other positive aspect.

Btw: was this introduced by a manager? How much does he or she pay per day to day mistake that happens? I think this counter question shows how absurd this is as management method.

Collapse
 
equiman profile image
Camilo Martinez

It was mentioned by tech leader because QA report same mistake over and ever again (on differents screens).

They talked, the whole team and agre this "taxes":

  • 1000 COP (0.33 U$) commit or pull request that can't be compiled (by Jenkins)
  • 1000 COP (0.33 U$) Missing field validation
  • 500 COP (0.15 U$) Spelling mistakes.
  • 2000 COP (0.65 U$) Tech leader mistakes

Money collected wold be used for buy beer on December.

Collapse
 
pchinery profile image
Philip • Edited

As the tech leader fee is double the price, it might be worth looking at, as the money goes into beer for the team in the end. An even softer approach would be to just give points and the person with the high score has to bake a cake in the end.

As long as this is done in a fun way with a little wink and not to but blame individual persons, it could work. As soon as it becomes a real punishment or could cost a developer a relevant part of the salary, it will get very serious and can cause more trouble than it actually solves (in my opinion).