Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
Yeah pair programming sucks. Talking and thinking at the same time doesn't work well. That's why chess players don't talk while they play.
I think pair programming sucks and is stupid as well. However, there are those out there who have had a positive experience with it. Who am I to say those people shouldn't do it?
Actually I love it. For example it's the perfect way to teach juniors. Just plan 2h a day pairing with them and their progress is incredible. I too learned some stuff from juniors that way.
And I like to do it with other seniors, too. Most of the time we come up with a much better solution together than we both would have alone. If you didn't have any of those experiences I really wonder why.
Mike9506611yMob programming? How about telling artists to do Mob painting? Or musicians to do Mob composition? Do you think they would be happy? Writing software is an artistic endeavor.
One of the main pleasures of being a developer is sitting alone, in peace and quiet, sipping on a cup of coffee, and creating something that is YOURS. That sense of satisfaction and pride one gets from this lost when working in groups. Spending hours discussing things like the best way to blink an LED or name a variable gets old fast. Having to tiptoe around fragile egos all day also gets old fast.
I recently left a job of 6 years because a newly hired director forced mob programming on the existing software team without asking anyone how they felt about it.
Managers, heed this warning: force this garbage on your devs at your own risk. I guarantee you will be resented for it and start losing good people.