Timeline for Is a coder that 'quality checks' bug fixes and bugs raised by testers a recognised role?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 7, 2013 at 15:17 | comment | added | MattDavey | I would advocate that all hotfixes are pair-programmed where at least one of the developers is a senior & has a breadth of experience in the system. | |
| Jan 7, 2013 at 14:11 | comment | added | Bart van Ingen Schenau | IME with complex systems, before an issue is assigned, or even prioritized, a quick pre-analysis is done to weed out any duplicate reports and to see if there is enough information present to be able to find the cause. This pre-analysis is often done by someone with above-average understanding of the complete system. It sounds like that is part of what @Flynn1179 is doing. | |
| Jan 7, 2013 at 13:47 | comment | added | Thomas Owens♦ | @DocBrown True. That's where things like peer reviews come in, though. Especially true with a new team member or someone working in an unfamiliar module - someone with more experience with the system and a better understanding of how it is designed and implemented can provide feedback and comments as well as answer questions during the investigate/fix/test cycle. | |
| Jan 7, 2013 at 13:40 | comment | added | Doc Brown | +1. Nevertheless it is not uncommon that some team members have a better understanding of the possible impacts of a bug fix than the programmer who creates the bug fix. | |
| Jan 7, 2013 at 13:29 | history | answered | Thomas Owens♦ | CC BY-SA 3.0 |