After a few weeks time I generally read the book Dreaming in Code, the following are some of their findings:
1. The power to do things
Whatever you do, have a goal and motivation to get things done both quality and time will have a very good effect, the software we do, too, our goal is to do a mythical kind of software, expected results What is the estimated cost (including time and money) about how much, what software to use after the promotion profits, as well as about future earnings, before doing had to think carefully, otherwise hard busy for a long time but only got some unused code stored in the computer and was not really aware of the project has been to what extent, and also how much manpower and resources into their own before they can see the results next, think really quite frightening, this way there is no power to get things done. It goes on is a vicious cycle, doing things that can succeed?
2. work and responsible attitude
No matter what the situation is in charge must be maintained at all times respect for what you do, and be accountable, not just to do things the attitude of a man of quality, in Hard Drive this book, about such story - Since Windows delays, BillG with SteveB final say - if Windows has not come out before the snow this year, you do not dry in here. The book does not say in detail SteveB come back again, and his team say what, but the next day a staff stationed in the office carrying a sleeping bag.
Many years later, Windows Vista also experienced a long delay, announced the delay after another, it was discovered that a well-known Windows team has been the VP pack up and go.
We look back at the Chandler project seven years of delays, the project manager had to resign something you did not happen? Maybe not. [There are a lot of people to leave, but no one is directly responsible for project delays] since my last delay is no punishment, then why did I have to Pinlelaoming next time to avoid delay it? So people have this lucky heart, there will be a next time is not responsible for, in case there next time, so employees do not accept the punishment would have been so not to make a change, of course, develop their own responsible attitude and spirit is their own make a performance basis.
3. The communication between the team and the customer
Not just this book, the book has a lot to write software engineering mention this kind of software a person to make a hero is gone, and now the project is team development, communication development process on It is extremely important. We can through various means such as QQ meeting to discuss job specifications and how to further develop. With customers can more clearly what customers want to know whether their results to be accepted. . .
It is a rough summary of the above points, continue to the next update.