Timeline for Pair Programming/Collaboration in a small company
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 15, 2013 at 13:00 | comment | added | Johannes S. | @RyanWilliams Code reviews are not about "breating down their neck". It's not about you controlling them. At our place, we use ReviewBoard as a platform and comment on each others code. There is no "hierarchy". The learning in this case is "implicit". They learn from reading your and their code, from your and the other devs questions and the answers/comments to those questions. And they get to know other parts of the code base, which is quite beneficial IMHO. | |
| Sep 6, 2013 at 2:59 | history | edited | user96303 | CC BY-SA 3.0 |
grammar
|
| Sep 3, 2013 at 2:56 | history | edited | user96303 | CC BY-SA 3.0 |
added 6 characters in body
|
| Aug 26, 2013 at 1:10 | vote | accept | Ryan Williams | ||
| Aug 28, 2013 at 1:37 | |||||
| Aug 26, 2013 at 1:10 | comment | added | Ryan Williams | I guess that's really what I'm afraid of. Thanks for the thoughts. I'm going to accept your answer for being the first. (There were a couple other good ones, too.) | |
| Aug 25, 2013 at 2:17 | comment | added | user96303 | If the pair programming relationship is one way, I'd suggest it wouldn't be engaging and perhaps even slightly patronizing to your co-workers. Depending on how you model it, this could quite easily come across as, "this is how I program and it's the best approach". You wouldn't actually call this pair programming since it doesn't have both components. | |
| Aug 25, 2013 at 2:04 | comment | added | Ryan Williams | One other thing. Do you think there is less benefit than it is worth to pair program with them, where when I am the driver? It could still be used as a way to point out best practices, and still have some input and feedback on what I am doing (even if the relationship would surely be unbalanced). | |
| Aug 25, 2013 at 1:55 | comment | added | Ryan Williams | I will take your thoughts into consideration. It's a bit to parse and rectify mentally against what we are currently doing. An honest feeling I have is a bit of insecurity in my position as lead developer. Not because I'm not comfortable from a skill-perspective, but rather because both of our other developers are older than myself (one significantly, one not), and one even has a couple more years of experience. That being the case, traditional code reviews would seem awkward, because I don't want to seem like I'm breathing down their necks. Then again, maybe that's what I have to do. | |
| Aug 25, 2013 at 1:35 | review | First posts | |||
| Aug 25, 2013 at 3:00 | |||||
| Aug 25, 2013 at 1:18 | history | answered | user96303 | CC BY-SA 3.0 |