2 added 74 characters in body
source | link

I once worked in that kind of environment and guess what? I left this place with rage and in very bad terms. And that is what you're going to suffer from if you indeed try to measure your developer's proficiency based on their bugs.

You're doing it all wrong. Here's how we fixed it back in the days:

Make a complex yet short printed list of the most important points.

  • Did you check that code for exploits and critical security holes?
  • Did you commented it well so if someones else go in there he or she could fixes it right away.
  • etc.

If someone does NOT check that list before releasing THEN you can blame him or her.

This is how things should go. Because if you start measuring bug, you'll gain very bad "karma" from your employee, everyone will hate you and act with you as if you were a dictator. And also you will give credit to those who does absolutely sweet-nothing!

Everyone makes mistakes and there's always THAT little thing that we don't remember before releasing, and this is why hotfixes exist!

I once worked in that kind of environment and guess what? I left this place with rage and in very bad terms. And that is what you're going to suffer from if you indeed try to measure your developer's proficiency based on their bugs.

You're doing it all wrong. Here's how we fixed it back in the days:

Make a complex yet short printed list of the most important points.

  • Did you check that code for exploits and critical security holes?
  • Did you commented it well so if someones else go in there he or she could fixes it right away.
  • etc.

If someone does NOT check that list before releasing THEN you can blame him or her.

This is how things should go. Because if you start measuring bug, you'll gain very bad "karma" from your employee, everyone will hate you and act with you as if you were a dictator.

Everyone makes mistakes and there's always THAT little thing that we don't remember before releasing, and this is why hotfixes exist!

I once worked in that kind of environment and guess what? I left this place with rage and in very bad terms. And that is what you're going to suffer from if you indeed try to measure your developer's proficiency based on their bugs.

You're doing it all wrong. Here's how we fixed it back in the days:

Make a complex yet short printed list of the most important points.

  • Did you check that code for exploits and critical security holes?
  • Did you commented it well so if someones else go in there he or she could fixes it right away.
  • etc.

If someone does NOT check that list before releasing THEN you can blame him or her.

This is how things should go. Because if you start measuring bug, you'll gain very bad "karma" from your employee, everyone will hate you and act with you as if you were a dictator. And also you will give credit to those who does absolutely sweet-nothing!

Everyone makes mistakes and there's always THAT little thing that we don't remember before releasing, and this is why hotfixes exist!

1
source | link

I once worked in that kind of environment and guess what? I left this place with rage and in very bad terms. And that is what you're going to suffer from if you indeed try to measure your developer's proficiency based on their bugs.

You're doing it all wrong. Here's how we fixed it back in the days:

Make a complex yet short printed list of the most important points.

  • Did you check that code for exploits and critical security holes?
  • Did you commented it well so if someones else go in there he or she could fixes it right away.
  • etc.

If someone does NOT check that list before releasing THEN you can blame him or her.

This is how things should go. Because if you start measuring bug, you'll gain very bad "karma" from your employee, everyone will hate you and act with you as if you were a dictator.

Everyone makes mistakes and there's always THAT little thing that we don't remember before releasing, and this is why hotfixes exist!