Cheng-yu yu

 Assign two People every part of Project  Review every line of code  Require codes sign off  Route good code examples for interview  Emphasize that code listing public assets  Reward good code

 Configuration management is the practice of identifying projects artifacts and handing changes systematically so that a system can maintain its integrity over time. Another name is “change control.” it include techniques for evaluating proposed changes, tracking changes and keeping copies of the system as its existed at various points in time.

 Requirements and Design Changes  Follow a systematic changes control procesure  Handle change require in groups  Estimate the cost of each change  Be wary of high change volumn  Establish a change control board or its equicalent in a way that makes sense for your project  Watch for bureaucracy, but don’t let the fear of bureaucracy preclude effective change control

 Software Code Change  Version control software  Tool version  Machine Configration  Backup Plan

 Estimate Approaches  Estimate objects  Allow time for estimate and plan it  Spell out software requreiment  Estimate a a lower level of detials  Use several different estimation techniques and compare the results  Reestimate perodically

 Estimation vs control :  how to control human and technical resources make on time delivery product  What do you do if you behind  Hope you will catch up  Expand team  Reduce the scope of the project

 Measurement of Projects  Be aware of measurement side effects  To against measurement is to argue that it is better not to know what’s really happing on your project

 How programmers spend their time :  programmers spend their time programming not only spend time on the meeting but also spend time on training, reading and just thinking 

 Variation in Performance and Quality  Individual variation  Team Variation  Physical Environments  Religious issue

 Your personal charter directly affect your ability writing computer programs, include humility, curiousty, intellectual honest and so on.  The characteristic of superior programmers have almost nothing do how smart you are.  To be a good programmers, develop right habits.

 Great programmers will be great intelligent ??  NO,  Keepong routines short reduces the load on your brains  Using conventions of all sorts free your brain

 Build your awareness of the development process  Expermint  Read about problems solving  Analysis and plan before you act  Learned about successful project  Read! Documentation is important

 Read other books  Affiliate with professionals  Make a commitment to professional development  Level 1: beginning  Level 2: Introductory  Level 3: Competency  Level 4: leadership

 Refusing to pretend you’re an expert when you are not  Readily admitting your mistakes  Try to understand a compiler warning rather than suppressing the message

 Clearly understanding your program not compiling it to see if it works  Providing realistic status reports  Providing realistic schedule estimate and holding your ground when management ask you to adjust them

 Communicating with other programmers team first then communicated to computers second  Excellent programmers learn how to work and play with other team members

 Deferring an unpleasant task  Doing an unpleasant task quickly to get it out  Writing a tool to do the unpleasant task so that you never have to do the task again

 Persistence  Stuck --> don’t give up  Frustrated --->try to find alternate way  Experiences  Using your experiences to solve problems  You lean job today-  help your feature job tomorrow

 Good charters is mainly a matter of having right habits.  Good coding practices cab be achieved either through enforced standards or through more light handed approach.  Measurement is a key to sucessful construction management.