> I'm not interested in opinions about mob programming, I have very positive experience with remote sessions :) Well, I am. Wtf is mob programming and who’s got hands-on-keyboard? Pair programming makes sense because a discussion can be held — mob programming makes me imagine twitch plays Pokémon
Sure, you can check out more here: https://www.remotemobprogramming.org/ Basically, one person writes the other discussion, and we switch every 20 minutes, so everybody can take part.
Ask HN: Would you like to join a mob programming group?
21–27 of 27 posts
Re: Ask HN: Would you like to join a mob programming group?
#22Re: Ask HN: Would you like to join a mob programming group?
#23Re: Ask HN: Would you like to join a mob programming group?
#24I'm totally down. I'm a verse developer.
Re: Ask HN: Would you like to join a mob programming group?
#25How can we get involved
Re: Ask HN: Would you like to join a mob programming group?
#26Mob programming seems to be a super inefficient way to develop software. Basically programming by committee?
It's like saying basketball is inefficient, when I pass the ball to a team mate I can loose it, better if I run the whole field on my own. Programming is mostly a team sport as well, involving backend and frontend engineers, qa, design, product owners.
I mean, I would say basketball is inefficient: having one person run the ball or maybe two reliable players pass it across the whole court definitely seems most efficient.
The only twist in basketball is that there's another team trying to stop you from achieving your goal (which would also add to the appeal of mob programming greatly!)
Re: Ask HN: Would you like to join a mob programming group?
#27> I'm not interested in opinions about mob programming, I have very positive experience with remote sessions :) Well, I am. Wtf is mob programming and who’s got hands-on-keyboard? Pair programming makes sense because a discussion can be held — mob programming makes me imagine twitch plays Pokémon
Sure, you can check out more here: https://www.remotemobprogramming.org/ Basically, one person writes the other discussion, and we switch every 20 minutes, so everybody can take part.
>We adopted the terminology from Code with the Wisdom of the Crowd by Mark Pearl:
>One person controls the keyboard, this is the typist. The rest of the mob discusses the problem, agrees on the solution, and instructs the typist. The typist follows their instructions, puts them into code, and may ask clarifying questions to understand the solution. The rest of the mob guides the typist as needed.
>We value the typist as they allow the rest of the mob to focus on solving the problem.
>The typist must not code on their own. This balances the participation of all team members and it reduces the dominance of strong characters.
That sounds horrible!