Code cleanliness: Code of Conduct for professional programmers (English version)

Clean coding: code for professional programmers (English version)
Basic Information
Author: [us] Robert C. Martin (Robert C. Martin) [Introduction by translators]
Press: Electronic Industry Press
ISBN: 9787121175633
Mounting time:
Published on: February 1, August 2012
Start: 16
Page number: 244
Version: 1-1
Category: Computer> Software and program design> comprehensive

For more information, code cleanliness: Code of professional programmers (English version)
Introduction
Computer books
Programmers who endure various uncertainties and continuous stress and are able to succeed share one feature: they are deeply concerned with Software creation practices. They all regard software as a craft. They are all experts. In Uncle Bob's opinion, "professional" programmers should not only possess professional skills, but also have a professional attitude, which is also the core of this book. Professional attitudes include how to develop software with honors, self-esteem, and pride, how to do well and make clean, how to communicate and estimate honestly, and how to make transparent and frank choices on difficulties, how to understand the responsibilities associated with professional knowledge.
Want to become a real software expert? The neat coding path: the Code of Conduct for professional programmers (English version) may be helpful to you.

Directory
Clean coding: code for professional programmers (English version)
Foreword XIII
Preface XIX
Acknowledgments XXIII
About the author XXIX
On the cover XXXI
Pre-requisite Introduction 1
Chapter 1 professionalism 7
Be careful what you ask for 8
Taking responsibility 8
First, do no harm 11
Work Ethic 16
Bibliography 22
Chapter 2 saying No 23
Adversarial roles 26
High stakes 29
Being a "Team player" 30
The cost of saying yes 36
Code impossible 41
Chapter 3 saying yes 45
A language of Commitment 47
Learning how to say "yes" 52
Conclusion 56
Chapter 4 coding 57
Preparedness 58
The flow zone 62
Writer's block 64
Debugging 66
Pacing yourself 69
Being late 71
Help 73
Bibliography 76
Chapter 5 test driven development 77
The jury is in 79
The Three Laws of TDD 79
What TDD is not 83
Bibliography 84
Chapter 6 practicing 85
Some background on practicing 86
The coding dojo 89
Broadening your experience 93
Conclusion 94
Bibliography 94
Chapter 7 acceptance testing 95
Communicating requirements 95
Access tance tests 100
Conclusion 111
Chapter 8 testing strategies 113
QA shocould find nothing 114
The test automation maid 115
Conclusion 119
Bibliography 119
Chapter 9 time management 121
Meetings 122
Focuses-Manna 127
Time Boxing and tomatoes 130
Avoidance 131
Blind alleys 131
Es, bogs, swamps, and other messes 132
Conclusion 133
Chapter 10 estimation 135
What is an estimate? 138
PERT 141
Estimating tasks 144
The law of large numbers 147
Conclusion 147
Bibliography 148
Chapter 11 pressure 149
Avoiding pressure 151
Handling pressure 153
Conclusion 155
Chapter 12 collaboration 157
Programmers versus people 159
Cerebellums 164
Conclusion 166
Chapter 13 teams and projects 167
Does it blend? 168
Conclusion 171
Bibliography 171
Chapter 14 mentoring, apprenticeship, and craftsmanship 173
Degrees of failure 174
Mentoring 174
Apprenticeship 180
Craftsmanship 184
Conclusion 185
Appendix A tooling 187
Tools 189
Source code control 189
IDE/Editor 194
Issue tracking 196
Continuous build 197
Unit testing tools 198
Component testing tools 199
Integration testing tools 200
UML/MDA 201
Conclusion 204
Index 205

This book is from: China Interactive publishing network