The Clean Coder

BookInfo

ISBN: 9780137081073	Number of Pages: 256
Publisher: Pearson Education	Book Title: The Clean Coder : a CODE of Conduct for Professional Programmers
Publication Year: 2011	Target Audience: Scholarly & Professional
Author: Robert Martin	Format: Trade Paperback

Abstract

Software quality is not only depend on architecture and project management, but also closely related to code quality. This point must be acknowledged by both the agile development school and the traditional development school.

The Clean Coder puts forward a view that the quality of code is directly proportional to its cleanliness. The clean code is not only reliable in quality, but also lays a good foundation for later maintenance and upgrading. As an outstanding person in the field of programming, the author of this book has given a series of effective clean code operation practices.

These practices are embodied as rules in this book, supplemented by positive and negative examples from actual projects. As long as these rules are followed, clean code can be written, thus effectively improving the code quality.

This book is intended for all coders and technical managers who are interested in improving code quality. The rules introduced in the book are all from the author’s many years of practical experience, covering many aspects of programming from naming to reconstruction.

About the Author

Robert C. Martin, a world famous programming master, a pioneer of design patterns and agile development, the Chief Chairman of Agile Alliance, and the former Chief editor in C++ report. He became a professional programmer in 1970s, later founded the company Object Mentor and served as president. Younger programmers often call him Uncle Bob.

Martin is also a prolific writer and has published hundreds of articles, papers and blog articles. He is the author of The Clean Coder, Agile Principles, Patterns, and Practices , UML for Java programmers, etc.

The Clean Coder PDF version is avaliable Later ,Please come back soon.

Table of Contents

Introduction

Chapter 1: Professionalism

Be Careful What You Ask For
Taking Responsibility
First, Do No Harm
Work Ethic
Bibliography

Chapter 2: Saying No

Adversarial Roles
High Stakes
Being a “Team Player”
The Cost of Saying Yes
Code Impossible

Chapter 3: Saying Yes

A Language of Commitment
Learning How to Say “Yes”
Conclusion

Chapter 4: Coding

Preparedness
The Flow Zone
Writer”s Block
Debugging
Pacing Yourself
Being Late
Help
Bibliography

Chapter 5: Test Driven Development

The Jury Is In
The Three Laws of TDD
What TDD Is Not
Bibliography

Chapter 6: Practicing

Some Background on Practicing
The Coding Dojo
Broadening Your Experience
Conclusion
Bibliography

Chapter 7: Acceptance Testing

Communicating Requirements
Acceptance Tests
Conclusion

Chapter 8: Testing Strategies

QA Should Find Nothing
The Test Automation Pyramid
Conclusion
Bibliography

Chapter 9: Time Management

Meetings
Focus-Manna
Time Boxing and Tomatoes
Avoidance
Blind Alleys
Marshes, Bogs, Swamps, and Other Messes
Conclusion

Chapter 10: Estimation

What Is an Estimate?
PERT
Estimating Tasks
The Law of Large Numbers
Conclusion
Bibliography

Chapter 11: Pressure

Avoiding Pressure
Handling Pressure
Conclusion

Chapter 12: Collaboration

Programmers versus People
Cerebellums
Conclusion

Chapter 13: Teams and Projects

Does It Blend?
Conclusion
Bibliography

Chapter 14: Mentoring, Apprenticeship, and Craftsmanship

Degrees of Failure
Mentoring
Apprenticeship
Craftsmanship
Conclusion
Appendix A: Tooling
Tools
Source Code Control
IDE/Editor
Issue Tracking
Continuous Build
Unit Testing Tools
Component Testing Tools
Integration Testing Tools
UML/MDA

Conclusion