1. A CODE OF CONDUCT FOR PROFESSIONAL
PROGRAMMERS

2. About me
Person Name Arseny Burekhin
Project Tobii
Position Team Leader
E-mail arbu@ciklum.com
www.ciklum.net 2

3. The Clean Coder
A CODE OF CONDUCT FOR PROFESSIONAL
PROGRAMMERS

4. What I will talk about
 First, Do Not Harm  Time Management and
 Work Ethic Estimation
 Saying No  Collaboration
 Saying Yes  Mentoring
 Coding  Tools
 TDD
 Practicing
 Testing Strategies

5. First, Do Not Harm
 Do not harm to function
 Do not harm to structure
 You must know it works
 QA should find nothing

6. WORK ETHIC
• Know your field
• Continuous Learning
• Practice
• Know Your Domain
• Identify with Your Employer/Customer

7. Saying No
 Adversarial Roles
 High Stakes
 Being a “Team Player”
 Is Good Code Impossible?

8. SAYING YES
• A Language of Commitment
• Recognizing Lack Of Commitment
• Learning How to Say “Yes”

9. CODING
• Preparedness
Code must work
Code must solve the problem
Code must fit well into the existed system
Code must be readable by other programmers
• 3 am Code
• The Flow Zone
• Writer ’s block
• Debugging
• Pacing yourself
• Help

10. TEST DRIVEN DEVELOPMENT
• The Three Laws of TDD
• Benefits
Certainty
Defect Injection Rate
Documentation
Design

11. PRACTICING
• The Coding Dojo
Kata
Wasa
• Broadening Your Experience
Open Source
Practice Ethics

12. TESTING STRATEGIES
•QA Should Find Nothing
• QA is part of the team
• QA as Specifies
• QA as Characterizers

13. TIME MANAGEMENT &
ESTIMATION
•BLIND ALLEYS
• MEETINGS
• TIME BOXING AND TOMATOES
• OTHER MESSES
• What Is An Estimate ?

14. COLLABORATION
• Programmers versus people
• Programmers versus programmers

15. MENTORING
•Degrees of failure
• Apprenticeship
• Craftsmanship

16. Tools
 SOURCE CODE CONTROL
 IDE / EDITOR
 ISSUE TRACKING
 CONTINUOUS BUILD
 UNIT TESTING TOOLS
 INTEGRATION TESTING TOOLS

17. Questions?