45 habits of an efficient programmer PDF

Download address: Download the network disk

Author Profile ...

Dr. Venkat Subramaniam

Founder of Agile Developer Company, an authoritative person for agility development. He has trained and mentored thousands of software developers across the United States, Canada, India and Europe, and has delivered speeches at various conferences. He is also the author of. NET Gotchas. You can contact him by venkats@agiledeveloper.com.

Andy Hunt

Agile Development Authority, founder of Agile Manifesto, founder of pragmatic programmers company. In addition to this book, he is a co-author of many award-winning and well-received books, including programming Ruby, the path of programmer cultivation-from small to expert, unit test in C # Edition-using NUnit, the Java version of Unit test-using JUnit, Version control-using CVS, and so on.Catalog ...The 1th chapter Agile--The way of efficient software development
2nd, Attitude decides everything.
1. Work
2. Haste to waste
3. Not to the people
4. Go all out of the way
The 3rd Chapter
5. Tracking Changes
6. Investing in the team
7. Know how to Discard
8. Break the casserole and ask the end
9. Grasp the development rhythm
4th. Deliver the software that the user wants
10. Let the customer make the decision
11. Let the design guide rather than manipulate the development
12. Rational use of technology
13. Maintain the ability to publish
14. Early integration, frequent integration
15. Early implementation of automated deployment
16. Get frequent feedback with demos
17. Use short iterations to publish incrementally
18. Fixed price means betrayal of commitment
5th. Agile Feedback
19. Guardian Angel
20. First use it to achieve it again
21. Different environment, there are different problems
22. Automatic Acceptance Test
23. Measure Real-world progress
24. Listen to the voice of the user
The 6th Chapter Agile Coding
25. Code to express intent clearly
26. Communicate in code
27. Dynamic evaluation Trade-offs
28. Incremental programming
29. Keep it simple
30. Writing the cohesive code
31. Tell, don't ask
32. Replacement according to the contract
7th Chapter Agile Debugging
33. Record the problem resolution log
34. Warnings are errors
35. Conquer the problem
36. Report all exceptions
37. Provide useful error messages
8th Chapter Agile Collaboration
38. Regular Appointment Schedule
39. Architects must write code
40. Implementing Code Ownership
41. Become a Mentor
42. Allow everyone to find a way
43. Share your code when you're ready
44. Do code review
45. Timely notification of progress and issues
The end of the 9th chapter: towards Agility
9.1 Only need a new habit
9.2 Saving the project on the verge of failure
9.3 Introducing Agility: A manager's Guide
9.4 Introducing Agility: A Programmer's Guide
Is the 9.5 over?
Appendix A Resources
Index

Download address: Download the network disk