Timeline for Should Junior Programmers be involved as code reviewers in the projects of Senior Programmers?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 12, 2013 at 22:48 | comment | added | Cascabel | Hm, I think we understand the OP differently - the post does say emphasis on learning, but it also says "involved as code reviewers", implying that the junior programmer is not the only person. | |
| Feb 12, 2013 at 19:35 | comment | added | mouviciel | @Jefromi: The OP did explicitly say that he/she want to set the purpose of code review to learning. I just say that this is not what they are meant for. | |
| Feb 12, 2013 at 17:36 | comment | added | Cascabel | The OP did explicitly say that the junior programmer has good skills. Less experience does not always mean lower-quality code reviews. | |
| Feb 12, 2013 at 10:09 | comment | added | yannis | Code reviews can be learning experiences. That said, I fully agree, that's not their primary purpose. Ideally all team members should be involved, but I see your point, it will take a while for a (truly) junior developer to be confident enough to point out flaws (assuming she can identify them first, which is also something I wouldn't honestly expect from a junior reviewing a senior's code). | |
| Feb 12, 2013 at 10:06 | history | answered | mouviciel | CC BY-SA 3.0 |