Go out of the trap of the software Workshop

The software workshop has been released for a whole year.

 

The press recently told me a few good news:

1. "Getting out of software Workshop" won the first place in Internet sales

2. Going out of the software workshop won the sixth name for Dangdang computer

3. The "out of software Workshop" won the tenth place in the field of excellence in computer science.

 

In the past year, "coming out of the software Workshop" has won the favor of many friends. However, the book I want to talk about has several traps. If it is not used properly, it will hurt myself. Here I will talk about some tips on how to use good books.

 

1. Do not be enthusiastic. Never be enthusiastic. Many of my friends have watched the excitement of "coming out of the software Workshop". They want to spread it to the R & D department, correct their R & D teams, and let their subordinates write their experiences. This is not a good thing for the spread of books. However, this is not a way to achieve the goal. I have also written this article in "coming out of the software Workshop" for many times. solving problems is just like playing the ice stick chopsticks game when I was a child. I need patience, persistence, calmness, and attention. This is especially important. Without making money, it is difficult to implement any idea in commercial machines. Without the painful money lessons of losing tickets at a loss, it is difficult to implement any idea in commercial machines. Many of our practices are helpless and we want to make a big list. Our customers are scolded for problems such as quality problems, pre-sales problems, after-sales problems, training problems, and project planning problems, it makes us unable to win a large order, and we have worked so hard to do a lot without being recognized or invisible to others. We just want the boss to let customers see that we have done a lot of things, but many things are not what they see in detail. We just want to protect ourselves. If you are not forced to be helpless, do not try the method in "getting out of software Workshop. Every enterprise has such problems, so don't worry about not complaining. Check whether the current model affects the boss's making money, whether it affects his or her own making money, and whether it makes your life better? Don't pay if there is no obvious return. Do not use too much power, boy, slowly, or slowly.

 

2. Someone also said to me, "Master Zhu, Which company do you work for? I want to follow you ". I smiled silently. Although the methods in the book are actually used in real projects and have received good results, we cannot use all the methods successfully in one project. We have never. Each project is always affected by many factors, such as the amount, time, customer personality, number of projects, concurrency, change of Customer business plans, customer wishes, and the boss's strategic play, all hope to use the successful experience, but it cannot be achieved every time. Every project has regrets, such a project is followed by a project. However, please believe that every method is proven to be effective, and this is not an obscenity. However, you should not expect to use it in a project. Based on the characteristics of your project, you can introduce appropriate methods in appropriate scenarios.

 

3. There are many methods in the book. Some methods are the final form. Of course they look good. In fact, in order to form a more complete and mature method, the initial method is simple. We are not afraid, and we have not given up. Of course, we have complained, but we have to continue to step forward after complaining about it. Even if the car is not pushed backwards. In my book, I also try my best to introduce what happened at the beginning and what happened, so I hope that you can start with your biggest headache when applying the Code, and first use the simplest method. Yes and no are qualitative differences. Yes, it is better than it is the difference in quantity. So no matter whether we have nothing or not, we have at least a penny now. Don't look down on a penny. At least we have a class. Yes, that's it. A little bit. If there is no chance, we will create an opportunity. We will wait for the opportunity to push the situation and the situation a little bit, one thing at a time to reverse the impression of others. Simplified. Identify what you want to achieve, identify your core issues, and think clearly about the route to implement it in the simplest way. Use Excel, Word, PPT, Visio, and so on first, or even excel first. You are used to it yourself, and your team is used to it, and then to a larger scope.

 

IV. The four carriages are fundamental. Some people see mountains and others see water. Some people think that "coming out of software Workshop" is a collection of ideas. Some people think that "coming out of software Workshop" is a ghost idea. But when I write, it refers to the future development of enterprises from the aspects of organizational structure, demand research, software design, Platform Framework Design, code development, code maintenance, customer customization, testing, documentation, implementation, training, service support, corporate culture, and enterprise development. IT personnel career development and self-improvement of professionalism. This is a complete Main Line. But I don't want to say so clearly that it will turn a book into a model. However, everyone faces different environments, different customers for each project, and different experiences and ideas, this is why many people have not applied the software engineering books abroad. This is why the MBA tutorial at Harvard Business School is case-based. IT management, R & D management, and implementation service management are all in the end or in the scope of management. The management is the same as that of production management. Everyone should have a proper view of software engineering and management.

 

5. Thinking and viewing problems are more important than anything else. I have never been away from enterprise informatization, so I am unfamiliar with Internet development management, consumer software development management, embedded development management, and outsourcing development management. Therefore, I have a lot of limitations. You can choose from the book to get your own useful things. Moreover, a book cannot carry so many satisfying things. Based on your own practical application, especially your attitude towards doing things, you can solve problems. I always think about the question: "What is the significance of this question? What if I don't solve it? Let's take a look at the problem ". As a matter of fact, many problems have no meaning at all, so there are two or three key links to a successful event. In addition, many times a problem is crossed by several problems. As long as each problem is isolated in a simple and crude manner, it is much simpler to crack each problem. In addition, I often seems to have gotten a bunch of things. I did not have a few problems. I have encountered this situation many times.

Online comment on "getting out of software Workshop:

Http://www.douban.com/subject/3319935/

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