Team solidarity
When it comes to software development, having two people work on the same project does not mean the shipping time is halved. Ever.
If you get your car stuck in the mud and no one’s coming to help, you’ll likely get out and push it as hard as you possibly can.
Now, put yourself on that same road, same situation, but this time you’re traveling with a few buddies. Almost guaranteed: no one will push at 100%.
Software developers benefit from understanding this implicit human behavior. Acting deliberately around it helps mitigate this team solidarity paradox. A simple example: task division. Keep one person focused on pressing the accelerator while the car is actually moving those few inches through the mud.
The paradox of the paradox is that some people will do more for others than they do for themselves. These are "heroes". They show up occasionally, but under sustained conditions, they still perform like regular humans.
Some keys to be less of an accomplice villain in this:
- Don’t default to helping. Pause and ask whether your involvement is actually required.
- Understand the project as a whole and where your role fits.
- Make ownership explicit. One problem, one owner.
- Express when you’re helping for convenience rather than necessity.
- Add to your set of rules one principle: keep the team away from muddy roads.