,
5 tweets,
2 min read
Read on Twitter
Thread: I‘ve been practicing #mobprogramming for a while. Every day that I am working alone now feels wrong. I make more mistakes, need more tries, forget things, have to actively and tediously synchronize with team members, have to wait for stuff, stumble upon stuff that (1/5)
other people did (alone) which is either bad or not easy to understand, am interrupted and have to switch tasks often, find the same thing implemented in many ways, have to review code, have my code reviewed, have to invest time in merging and rebasing, don‘t exactly know (2/5)
where we are and what‘s next, ...
We have been trained to work alone. It‘s our comfort zone. The safest space is the space that we don‘t have to share. That‘s why I understand that people want to work alone. But working alone is just wasteful. It increases the amount of (3/5)
We have been trained to work alone. It‘s our comfort zone. The safest space is the space that we don‘t have to share. That‘s why I understand that people want to work alone. But working alone is just wasteful. It increases the amount of (3/5)
partially done work, the number of times that things need to be learned, the number of handoffs, the length of delays, task switching and, because we are human, defects. I‘d love to be able to work alone - in my comfort zone, in my personal safe space. However, it (4/5)
proves to be inefficient, unproductive and wasteful.
And yes, this is a rant. Too often I have to argue about the productivity of parallelization fallacy. Mob programming is far beyond being an experiment. (5/5)
And yes, this is a rant. Too often I have to argue about the productivity of parallelization fallacy. Mob programming is far beyond being an experiment. (5/5)
