Thank you for the article, it was very informative and meaningful. My feeling when I was active here is that I could openly express my ideas (which sometimes where guided by a lack of programming knowledege) but still they were listened to, commented by the core developers, and some times used. So having read the article, I guess this answers your question ;)
My summary of the article would be that the key points for a team to be good are: - Psycological safety - Similar amount of words expressed by each component of the team - Group "Traditions" or dynamic, which are more difficult to define and vary much among different teams. These include the way the group dialogues, how they treat conversations, jokes, etc. There is not a good way to do, this is estabilished naturally by each team and will be good or bad depending on the first two components. On Friday, February 26, 2016 at 10:27:08 PM UTC+1, Edward K. Ream wrote: > > I highly recommend this article: What Google Learned From Its Quest to > Build the Perfect Team > <http://www.nytimes.com/2016/02/28/magazine/what-google-learned-from-its-quest-to-build-the-perfect-team.html?_r=1>. > > See if you can guess what the key points are. > > I won't let the cat out of the bag, but I think the answers they > discovered make sense. And I think Leo's core developers do pretty well on > those measures. What do you think? > > Edward > > <http://www.nytimes.com/2016/02/28/magazine/what-google-learned-from-its-quest-to-build-the-perfect-team.html?_r=1> > -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to leo-editor@googlegroups.com. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
