"Internal open source"

I bought my tail in July.ProgramEmployee No. July. Here is an articleArticleIt attracted me to "inspire enterprise innovation: Internal open source ".

 

The content mainly refers to the author's observation of Open SourceCommunityIs introduced into the enterprise. Enhance team openness and creativity and cohesion. If you are interested, you can check the programmer's July or read the original "Beautiful teams". The magazine is an excerpt from the book.

 

Recently, I am very concerned about the openness and atmosphere of my team, because my experiences in working in different departments have made me feel almost different.

About a month after I first arrived at department a, I found that the internal atmosphere of the Department was depressing, uncreative, and the communication was unfavorable. It was quite closed. So I wrote an email to the department leaders asking them if they can run our internal projects and frameworks in an open-source manner. It may be that I was born to be wretched, and the department director must treat me as a liar to defraud the company.Code, Rejected me and continued to maintain the original running mode. Later, I also reflected on whether my approach was wrong and I did not investigate it in depth.There is nothing to blame here. Thanks to the current strong KPI pressure, we are already thankful to anyone who has the energy to take care of this task. Not easy.

 

Later, I went to department B, which is open to many users. Although I don't want to talk about the "Open Source" mode, I have three important factors: code access and document access, code record access. This gives us a wonderful feeling.

 

Team building is not that simple, and often involves some details, but small things make a big difference. They are all shouting for openness, which is really not easy.