The Clean Coder: a code of Conduct For Professional Programmers

M
E N TO R I N G
I have a whole chapter on this topic later in the book. For now let me simply say 
that the training of less experienced programmers is the responsibility of those 
who have more experience. Training courses don’t cut it. Books don’t cut it. 
Nothing can bring a young software developer to high performance quicker 
6. This is far more true of men than women. I had a wonderful conversation with @desi (Desi McAdam, 
founder of DevChix) about what motivates women programmers. I told her that when I got a program 
working, it was like slaying the great beast. She told me that for her and other women she had spoken to, 
the act of writing code was an act of nurturing creation.

---

C
HAPTER
 4 C
ODING
76
than his own drive, and effective mentoring by his seniors. Therefore, once 
again, it is a matter of professional ethics for senior programmers to spend time 
taking younger programmers under their wing and mentoring them. By the 
same token, those younger programmers have a professional duty to seek out 
such mentoring from their seniors.
B
I B L I O G R A P H Y
[Martin09]:
Robert C. Martin, 
Clean Code
, Upper Saddle River, NJ: Prentice 
Hall, 2009.
[Martin03]:
Robert C. Martin, 
Agile Software Development: Principles, Patterns, 
and Practices
, Upper Saddle River, NJ: Prentice Hall, 2003.

---

205
I
N D E X
A
Acceptance tests
automated, 97–99
communication and, 97
continuous integration and,
104–105
definition of, 94
developer’s role in, 100–101
extra work and, 99
GUIs and, 103–105
negotiation and, 101–102
passive aggression and, 101–102
timing of, 99–100
unit tests and, 102–103
writers of, 99–100
Adversarial roles, 20–23
Affinity estimation, 140–141
Ambiguity, in requirements, 92–94
Apologies, 6
Apprentices, 183
Apprenticeship, 180–184
Arguments, in meetings, 120–121
Arrogance, 16
Automated acceptance testing, 97–99
Automated quality assurance, 8
Avoidance, 125
B
Blind alleys, 125–126
Bossavit, Laurent, 83
Bowling Game,
 83
Branching, 191
Bug counts, 197
Business goals, 154
C
Caffeine, 122
Certainty, 74
Code
control, 189–194
owned, 157
3 AM, 53–54
worry, 54–55
Coding Dojo,
 83–87
Collaboration, 14, 151–160
Collective ownership, 157–158

---