51–56 of 56 posts
Anyone have a non-paywall link?
Also, out of curiosity, who votes these up?
Earlier quoted context omitted.
We don't "preach" pair programming. It's how we work. We're hiring. If you want to see what it's like, apply. We use pair programming sessions as the core of our hiring process.
You didn't answer my question. Why wouldn't Pair Programing concept be applicable to CEO's and Other Executives? Why only programmers/Designers need to be Pair Programmed?
Typically at Pivotal we have a single Product Manager per product, who acts as the single decision point for how to prioritise the stories and bugs in the backlog.
This increases the odds that a clear product direction will emerge -- it avoids the mum and dad game. The Product Manager and the team do most of the planning for a week at an Iteration Planning Meeting, and the PM remains available during the week to answer questions, accept stories and to update priorities according to changing circumstances.
Once you know what to work on, it's important to build the system correctly, and to ensure that there is shared understanding of how it is going to work.
Pair programming with frequent rotations is an outstanding way to do that.
Incidentally, as it happens, I've seen Pivotal management pairing on management problems. And they retain the habits of communicating clearly, openly and frequently with each other and everyone else.
I've also seen Product Managers pairing as well, typically when we have provided a PM from Labs to work with, and help train, someone from the client who will take over as Product Manager.
Earlier quoted context omitted.
ah, right, that's why I don't work there, I had forgotten.
I don't understand the ire. It's a straight up great place to work.
Earlier quoted context omitted.
I don't understand the ire. It's a straight up great place to work.
it's great if you like to pair program every day. I get sick of pairing after about 3 hours. So it's not one-size-fits-all but I often meet people who can't imagine disliking pairing and try to convince me that my lived experience is somehow incorrect but theirs is accurate.
Personally, I agree with you: pair programming is not suitable for everyone. After a day of pairing I definitely want some quiet time.
We recently had an energetic internal discussion about whether we are simply selecting for extraversion in our process.
I suspect we're probably filtering out very strong introverts, but I've honestly seen a wide band of personalities. I've worked with men and women ranging from those who are chatty as I am, to the downright laconic. Some who want to socialise after work, to others like me who just want to go home for some personal time.
Earlier quoted context omitted.
I was a Software Engineering intern on an ads product team at Facebook last summer. My experience was almost exactly the opposite of what you assume here. Most people worked 7-8 hour days. I stayed plenty of late nights because I was dead-set on getting a full-time offer, but I was literally the only one on my entire floor most nights (including interns). On the off chance someone stopped in late and saw me, they wer…
So, did you end up getting a full-time offer?