The fact that devs are arguing whether something was a bug definitely is a red flag that this system is bad for the team, and the organization as a whole. It seems to me the problem is deeper than just devs making mistakes, so it probably won't be fixed by penalizing them. If the org is serious about quality, then they should probably examine whether the software is designed in such a way that devs can produce bug free code.
The practice itself is definitely borderline. I suppose it is similar to a "swear jar". In the dev context, maybe that could be making the same common mistakes over and over. The "bug jar" would really only work if the group agrees it is a problem and wants to take that step as a learning reinforcement aid. Trying to inflict it on the team through management would be absolutely horrible.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
The fact that devs are arguing whether something was a bug definitely is a red flag that this system is bad for the team, and the organization as a whole. It seems to me the problem is deeper than just devs making mistakes, so it probably won't be fixed by penalizing them. If the org is serious about quality, then they should probably examine whether the software is designed in such a way that devs can produce bug free code.
The practice itself is definitely borderline. I suppose it is similar to a "swear jar". In the dev context, maybe that could be making the same common mistakes over and over. The "bug jar" would really only work if the group agrees it is a problem and wants to take that step as a learning reinforcement aid. Trying to inflict it on the team through management would be absolutely horrible.