Hi All,

I am with this new company... and they have this habit of pair programming... I can't understand why? I just HATE that!!!
I can understand if they are technically onboarding you or you are stuck with a task and ask for help...but NOT for every task!!!
I don't want to change their way of doing things... I'm the new guy but I can't just think and code with lots of people thinking loud and dictating...
I now just sit back and watch... I'll stop here

Eric

 

hi E,
Do you have a question that we can maybe answer.?
E

 

I don’t even know what “pair programming“ is.
Sounds like some way of programming two microcontrollers at the same time.

 

hi E,
Do you have a question that we can maybe answer.?
E

I actually I have no question... just complaining... and I want to program myself... not with a bunch of people at the same time.

 

I don’t even know what “pair programming“ is.
Sounds like some way of programming two microcontrollers at the same time.

It's the stupidest thing ever! Waste of time and resources!

 

hi Eric.
Your posts are not explaining what help you are expecting from us.?

Moderation.

 

Pair Progamming is part of Agile Development. It's a quality control and cross training method. There is a lot of research that says it's very effective at reducing bugs and improving the quality of the code.

Basically, two programmers work together, one "drives", actually writing code and typing, the other does a line-at-a-time code review checking for errors and making suggestions about methods. There are different ways to pair people up, two experts, an expert and a novice, or two novices.

This last might sound weird but two novices do better together than alone.

I actually like pair programming and did it before it was cool. Some of our best projects went that way, and I can attest it does have the benefits attributed to it. Of course, not everyone will fit with it, and it can be a reason someone won't succeed in a shop that uses it.

 

You are an ACC fanatic!
Get back in the fight, go back to work go for the juggler show them how it's done.
You picked that avatar for a reason now get to it!

 

I'd rather like to work alone and have someone review my work before merging code. And I work at my own time. I just HATE that... why have 5 developers on a single task??? What I see is 1 - 2 doing the work and the others watching... and pair programming the whole day... #Smh

Anyway I was just sharing my story...

 

You are an ACC fanatic!
Get back in the fight, go back to work go for the juggler show them how it's done.
You picked that avatar for a reason now get to it!

You did not get my point! Anyway...

 

I'd rather like to work alone and have someone review my work before merging code. And I work at my own time. I just HATE that... why have 5 developers on a single task??? What I see is 1 - 2 doing the work and the others watching... and pair programming the whole day... #Smh

Anyway I was just sharing my story...

When PP is done properly the “watchers“ are performing a constant error correction function, as well as learning if the ”driver” is more experienced. Actual metrics show an improvement in productivity and quality of code.

While I can see that you don’t like it, the surveys I have seen have some high 90s percentage of programmers preferring it.

 

When PP is done properly the “watchers“ are performing a constant error correction function, as well as learning if the ”driver” is more experienced. Actual metrics show an improvement in productivity and quality of code.

While I can see that you don’t like it, the surveys I have seen have some high 90s percentage of programmers preferring it.

Okay @Yaakov !

 

About 40 years ago, I was talking with a colleague about a writing a Pascal compiler. He said let’s do it! I sat at the terminal, and he opened Wirth‘s book to the syntax diagram. In about an hour, we had a working parser. It was amazing. The two of us remained focused and “just did it” in a way neither of us could have alone.

Like any tool, pair programming can be used correctly or abused. I think it has some uses but should not be used indiscriminately.

Bob

 

I have someone with me at all times when I do my coding, his name is compiler, and he's my best friend.

 

I have someone with me at all times when I do my coding, his name is compiler, and he's my best friend.

That's a funny name for a dog.

 

As I see it, if you're not going to get with the program, the honorable thing to do is admit it and resign. It would be dishonest of you to continue in your present position while sabotaging their efforts to produce a quality product. The next time, ask better questions during the interview to avoid a repeat of this impending disaster. The only alternative is to salute smartly and say yessir! -- right away sir. Do not let this situation continue to fester.

 

The computer industry funded strategies to be more productive with the development of software.
In baseball all the outfielders rush in to catch a flyball. It is the calling out " I have it! " gives a perceived confidence switching from observer to proactive assertiveness in teamwork, however we sometimes we fumble and drop the ball. How do we talk to ourselves?
The coach sends you to the gym the trainer has you work on improving some skill sets. You become confident with disciplined workout
breathing and exercising until the problem naturally disappears. The monster fades into background.

Overcoming math exam anxiety is sometimes in the approach. The confidence comes with preparing in such a way to familiarize with the characteristics of each type of problem. Setting up the mechanics of the expression. The monster is our past negative experience.

 

You did not get my point! Anyway...

I just thought you needed a little pep talk.
Obviously it was a syntax error on your part.

 

I have never done pair programming and don't need to... can't focus and write code with a bunch of people talking at same time...
I have always provided quality code/work... that being said, I am a good team player though!
Anyway not my company... will do as required but on the first occasion I will code solo!!!
Btw, planning on build my own company very soon...

 

When PP is done properly...

Even when it is done properly, The biggest a-hole of the team often controls the conversation and tries to argue the benefits if his programming strategy until his last breath and others submit not because the a-hole is right, but just because they want the the project to move forward. If someone likes Agile development, and thinks it works well, that person is likely the a-hole of any agile team he's been on.