Timeline for Should I accept a job if pair programming is required?
Current License: CC BY-SA 2.5
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 18, 2014 at 11:45 | comment | added | Giorgio | @Wizard: I find with pair programming you discuss too many insignificant details: there is a lot of noise that slows down your train of thoughts and makes you less efficient. Other people find it stimulating and like the unstructured but continuous feedback they get. Some people say I am an individualist, I object that you can work as a team and still be structured, in the same way as a soccer team occupy the whole playground instead of going all where the ball is. Anyway, I think it is a matter of how each programmer works and not all programmers work in the same way. | |
| Dec 18, 2014 at 11:43 | comment | added | Giorgio | @Wizard: Some people like pair programming, I don't. I prefer to discuss the structure of the code in advance, then do the coding, then do a code review. This puts a filter between myself and my colleagues so that we only exchange relevant information. | |
| Sep 29, 2010 at 1:31 | comment | added | dash-tom-bang | +1 for honesty. :) It's not for everyone, indeed. | |
| Sep 28, 2010 at 18:54 | history | answered | Wizard | CC BY-SA 2.5 |