In the face of principles, everyone is equal, so that we can get out of the software workshop-51. com, said the president of technology.

Zhu gave me a book, "coming out of the software Workshop", and hoped that I could write a preface to the new version. I was surprised at the beginning that it was just a software developer's experience, not a masterpiece. After receiving the book, I introduced it to several colleagues. Unexpectedly, many people have read this book and I highly recommend it to Zhu. I was flattered by this. I have been away from the first-line development for many years. How can I write a sequence for such a very important technical management book?

Fortunately, I am still working in a technology company and working in charge of technical lines. As an Internet company with more than 200 programmers, our biggest taboo is that various project teams also adopt workshop-style development management and systematic O & M. Going out of the software workshop is a kind of management thinking, rather than providing some methods. Most of the time, people's thoughts decide to act. When you know that doing something is obviously wrong, you will choose the right method.

51.com from 3 ~ 5 technicians to 30 ~ 50 people, and then to more than 300 people. 51.com has been rated by Baidu as the best website for Web user interaction for two consecutive years. Maybe only our programmers can understand the meaning of this website. Upload 10 million photos, 5 million diaries, and 2 million group posts every day. And hundreds of millions of interactions between users. All of them must be saved in the system and each user needs to be instantly transmitted. These massive amounts of information need to be stored in online databases. As new users grow, old users continue to accumulate. The data stored in the system is still expanding. Another feature of the Internet system is that software updates are faster than clients and are released every day.

All of this puts a lot of pressure on technology. So many people, how to work together, how to reduce the impact of association among such functions, modules, and projects. The only way to do this is to get out of the software workshop. First of all, in our thinking, we constantly let every technician understand that we are no longer a workshop, and we must not use the workshop-style work model to do 51 things. Secondly, more importantly, we should constantly establish various R & D workflows, launch processes, and quality assurance processes in our work. And as the highest working principle and requirements in the company. No matter how much credit you have earned and how powerful you are, everyone is equal in front of these principles.

As we all know, the most difficult thing for people to change is their habits. Just like how difficult it is to remove this selfish thinking that ensures survival and perfunctory next generation is a deep-rooted thinking since the emergence of life. It is indeed difficult to use thousands of years of civilization to transform the ideas that have taken place over billions of years. Similarly, the free and casual design is also deeply rooted in Every programmer's mind. "I can do well without affecting other people's things." These things are very simple, there is no need to go through so many procedures. "Just do my own things well. How can I work with others? They can find a solution on their own", "This is impossible, you don't have to waste time discussing it "...... think about it. Do you and your technical colleagues often have these ideas?

Therefore, I highly admire Zhu's book. He systematically tells how an enterprise gets out of a software workshop, not only in terms of ideology, but also in terms of action and system assurance.

Online Ordering of "getting out of software Workshop:

Internet: http://www.china-pub.com/508874

Zhuo Yue Network: http://www.amazon.cn/mn/detailApp? Prodid = bkbk812538 & ref = gs_ts & uid = 168-8093432-0389064

Dangdang Network: http://product.dangdang.com/product.aspx? Product_id = 20435119