@mcc @glyph @mhoye I had that argument with a previous employer over mob programming.
They were trying to make everyone do it, it was burning some of us out.
Their response was “you can just not do it and the rest of the team will do it without you”.
Well, oh Einstein of managers, what do you think is going to happen when all the tools and communication structures the team uses assume mob programming, just like is required to do it properly? It’s not a real option to just not engage. You’ve just forced several of your staff out of a job because it was that or burning them out within weeks, and you’ve managed to paint it as their fault.
Ever since then I’ve been incredibly cynical about any “cultural shifts”. If it’s optional then it’s totally not optional they just don’t want to take the responsibility.
@glyph @griotspeak @mcc @mhoye with the “optional” part, at least in pairing, a big part of that is culture.
There’s a shift to be made in a team from “a group of individual contributors” to “we all sink or swim together, and it’s the job of the experienced members to lift up their juniors”.
This is, and again I speak from experience, a very difficult shift. But it makes a massive difference to both morale and productivity.
I’m lucky to work in a team where the senior staff are all of that mindset and we’re able to propagate it to anyone who joins. Honestly, it’s the only reason I’m still here.
But again, you need a bunch of powerful and emotionally intelligent people to set that baseline. And that’s… not guaranteed in engineering teams.
@glyph @griotspeak @mcc @mhoye sorry, to clarify, by “optional” I mean the focus in this sort of culture is to provide for the needs of the individual. So if someone says they work best going off alone, we’ve built up enough trust to pack them a metaphorical lunch box and send them on their way.
Again. Kind of a unicorn culture and I’m not sure I’ll ever see this again.