Is there a pattern to collaboration?
Development is a collaborative sport. But so much of it is an individual's journey through problems. While it is an open secret that more eyes on a piece of code, makes better code, what is it the stops us from implementing these collaboration practices while writing code?
I wonder if it is the up-front cost versus the apparent rewards. Much like the concept of a positive externality (from economics) where, the overall good that say pair-programming has, or code reviewing before PR's does on the general app health, is not effectively correlated to the action.
So is there a pattern you follow when it comes to collaboration?
Top comments (1)
When I think about collaborating with my teammates, the things that come to mind are:
But I actually don't think these are the most common&important ways we collaborate. The small, quick questions we ask each other multiple times per day are the moments where one bit of information leads to another and we end up investigating a bug together or discussing a new feature.