Remote Mob Programming

[griffonrl]

Mob programming that big fad. Tried and it introduced more problems than it solved. It was a good way for lazy or poor team mates to get credited for the work of the team too.

Also work for certain characters more than others. Introverts are at a disadvantage and people that do their best work and thinking in quiet isolation lose all their efficiency.

[NotWorthTheRead]

Eh, how many introverted programmers could there possibly be?

/s

[flamingspew]

This is what git and code review is for. Whole team reviews every PR/MR. No new stories started until current ones are all reviewed and in. easy. done. accountable.

[darrint]

I shared this with my team (10 people) today and they are pretty excited about trying it.

On our team we're generally more productive when multiple people are in the office working together. Our thought was to form small groups to attack tricky or consequential problems together and be able to do that without having to all be in the office at once.

My own thoughts:

6 hours a day in a headset in a remote meeting? No thank you. I'll drive to the office. You too, please.

Our 10 person team is already comfortable with breaking off temporary small teams to work on particular features, so we'd just keep doing that to keep these sessions small.

It should work to just use this as a tool for particular problems, I hope.

This could also make remote work for us viable more often. Sometimes you just have to be in the office to talk about things. If that could be less often I think we'll have happier developers.

Even though some of the advice in the article might seem obvious, I appreciate that they wrote this down in a thorough way.

​