undefined | Better HN

0 pointssunir14y ago0 comments

Well there is the intense XP understanding of pair programming, and then there is just sitting next to someone while they code version of pair programming. I can't believe anyone hasn't done something in that spectrum.

Even for juniors and new grads, at school people code next to each other all the time.

0 comments

7 comments · 3 top-level

fogus14y ago· 2 in thread

    sitting next to someone while they code

Then that's not pair programming. Pairing is an act of give and take, Ying and Yang, Ping and Pong, and sometimes Tweedledee and Tweedledumb. Sitting next to someone looking over their shoulder solving a problem that you know the answer to is not pair programming. There is no act of mutual discovery at all.

sunirOP14y ago

Why limit interview questions to problems you already know the answer to? You can have them help you with some problem in your actual codebase you're already working on.

kooshball14y ago

> You can have them help you with some problem in your actual codebase you're already working on.

This is a terrible idea. If they come up with a brilliant solution can you actually use this in production? Who owns the code they write during an interview?

HeyLaughingBoy14y ago· 2 in thread

I can't believe anyone hasn't done something in that spectrum

The last time I did anything like that was over 10 years ago. How would that skew your hiring process?

sunirOP14y ago

In my case, I may not hire you. Why haven't you worked with another developer in 10 years?

HeyLaughingBoy14y ago

I have worked with many, many developers. I just don't sit down next to them watching them program, or them watching me.

I have pair programmed (over 10 years ago) and I never saw any benefit from it. I work in an environment where every line of code checked into the repository is reviewed and documented in agonizing detail (welcome to the wonderful world of Medical Device software!) and I completely fail to see the benefit of pair programming.

bethling14y ago

I don't think I've ever worked in an environment where that's been something that happens all the time. Maybe occasionally being with someone while they try to sort out a bug.

But actually creating new code with someone sitting there - that's something that's not something I've seen often

j / k navigate · click thread line to collapse

0 comments

7 comments · 3 top-level

fogus14y ago· 2 in thread

    sitting next to someone while they code

sunirOP14y ago

Why limit interview questions to problems you already know the answer to? You can have them help you with some problem in your actual codebase you're already working on.

kooshball14y ago

> You can have them help you with some problem in your actual codebase you're already working on.

This is a terrible idea. If they come up with a brilliant solution can you actually use this in production? Who owns the code they write during an interview?

HeyLaughingBoy14y ago· 2 in thread

I can't believe anyone hasn't done something in that spectrum

The last time I did anything like that was over 10 years ago. How would that skew your hiring process?

sunirOP14y ago

In my case, I may not hire you. Why haven't you worked with another developer in 10 years?

HeyLaughingBoy14y ago

I have worked with many, many developers. I just don't sit down next to them watching them program, or them watching me.

bethling14y ago

I don't think I've ever worked in an environment where that's been something that happens all the time. Maybe occasionally being with someone while they try to sort out a bug.

But actually creating new code with someone sitting there - that's something that's not something I've seen often

j / k navigate · click thread line to collapse