Open source communities are often very strict in their adherence to basic principles of communication as without such rigorous, yet limited, rules the general goal of the projects would never be achieved since the maintainers would banging their heads together to just understand what others are trying to do, integrating alien code would be out of question. Although this creates a threshold which prevents total noobs from entering the community, it also works as a weed out process to let the most motivated to pass through and join the herd.
Now if this concept is ported to real world of blood and flesh, I would argue that there is much to be benefit from. Although huge volunteer based projects survive and thrive very well, I can easily observed that their actual rate of efficiency is very low. The reason for that is every person has an unique take on the little tasks which hold everything together and most are unwilling to let go of those habits for organizational benefit, because it it unnecessary for most personally. So, if the basic operations are predefined in, the basic process of communication would be much simpler. A very simple aspect would be documentation. In programming, without extensive documentation, developers would have to jump into every alien classes and abstractions to figure out their behavior and it can be a very time consuming process; so most open source projects have decent documentations needed for daily operation. But the same is not true of most organizations run by students in schools and colleges; when they divide up the work among each other and make implementations as necessary, no one records their approach or methods; so if your friend want to cover for your job of file sorting, he has to learn your process through trail and error or develop his process which can clash with your current system. Thus we all lose time, regardless of the pathway.
So I would advocate simple routines for members in all clubs in schools and universities so that people can explore their skills of problem solving in much more complicated topics and communicate their solutions using the simple set of precedences which is known to all. This harmony prevails........
Now if this concept is ported to real world of blood and flesh, I would argue that there is much to be benefit from. Although huge volunteer based projects survive and thrive very well, I can easily observed that their actual rate of efficiency is very low. The reason for that is every person has an unique take on the little tasks which hold everything together and most are unwilling to let go of those habits for organizational benefit, because it it unnecessary for most personally. So, if the basic operations are predefined in, the basic process of communication would be much simpler. A very simple aspect would be documentation. In programming, without extensive documentation, developers would have to jump into every alien classes and abstractions to figure out their behavior and it can be a very time consuming process; so most open source projects have decent documentations needed for daily operation. But the same is not true of most organizations run by students in schools and colleges; when they divide up the work among each other and make implementations as necessary, no one records their approach or methods; so if your friend want to cover for your job of file sorting, he has to learn your process through trail and error or develop his process which can clash with your current system. Thus we all lose time, regardless of the pathway.
So I would advocate simple routines for members in all clubs in schools and universities so that people can explore their skills of problem solving in much more complicated topics and communicate their solutions using the simple set of precedences which is known to all. This harmony prevails........