Timeline for Is Pair Programming also used to train less experienced developers and bring them up to speed?
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 12, 2013 at 0:15 | comment | added | Riga | @Aaronaught I guess you are arguing for the sake of arguing. As you have stated period of time makes sense. What is the problem then? If you are the guy who knows everything about a person after the interview then wow, you are super cool guy I never met. My experience can't be alienated from me. Interview gives you understanding whether the guy will manage to get things done. Other things is a long story and it is a good idea to start with pair programming. Your "true" understanding can't override this fact. | |
| Sep 11, 2013 at 23:56 | comment | added | Aaronaught | And there's a difference between one week of buddying up and 6 months of working on the same team. Point is, you should have a pretty good idea of how a person codes and approaches problems before you even hire them in the first place. | |
| Sep 11, 2013 at 22:32 | comment | added | Riga | @Aaronaught there is difference between a two hours interview and one week cooperation, isn't it? | |
| Sep 11, 2013 at 0:37 | comment | added | Aaronaught | I'm pretty sure that the interview is where you are supposed to figure out how someone thinks and introduce them to the culture. | |
| Sep 10, 2013 at 20:24 | history | edited | Riga | CC BY-SA 3.0 | added 123 characters in body |
| Sep 10, 2013 at 20:16 | history | answered | Riga | CC BY-SA 3.0 |