4 ms·
My employer does this in-house, by pairing a programmer up with a more experienced programmer or architect in roughly the same field, and having them review the
by skrebbel 14y ago
My employer does this in-house, by pairing a programmer up with a more experienced programmer or architect in roughly the same field, and having them review the programmer's work on a regular basis. I bet there's many firms with a system somewhat like this.
That said, if your team does peer code reviews, you get a lot of that coaching that you ask for, directly from your team members.
In fact, if your workplace doesn't have any way by which you can regularly collect feedback on your work, I'd be very worried. If nobody cares about the quality you produce, chances are small they care much about what you do at all. In any sufficiently important team, code reviews are a must in order to guarantee a sufficient level of quality.
- asher_ 14y agoI work in a small psychology research lab in a university. I am one (the senior) of only two programmers. I work here because I am passionate about the problems I get to work on, as well as the freedoms afforded to me. Since I am in this situation, code reviews and pair programming are of limited value to me, although we do them so I can help my junior colleague.