3 ms·
forcing them to have written tests beforehand would probably have avoided many of them in the first place I bet. What you describe could be dealt with by havin
by mgkimsal 16y ago
forcing them to have written tests beforehand would probably have avoided many of them in the first place I bet.
What you describe could be dealt with by having a team lead review things and assign some of the bugs back to the original developers. Done right, this can indeed increase some quality issues over the long haul.
The problem with this can often be the bugs are there not because they're lazy but because they really don't know a good way to solve the issue, and may not even have recognized the bug potential at the start. The 'fresh pair of eyes' argument has a lot of merit, but it tends to result in other people cleaning up for the original devs, which you're trying to avoid (I don't blame you).
Talk with the team lead(s) and see if they can divvy up some bugs back to the original devs, then track if those same mistakes get made by the same people or not.