The document discusses the principles and importance of clean code, emphasizing that well-written code should be elegant, efficient, and easy to maintain. It highlights key practices such as meaningful naming conventions, the single responsibility principle for methods and classes, and effective error handling. Ultimately, the document advocates for a disciplined approach to coding that prioritizes readability and maintainability.

1. Clean code
Better coding practices

2. What is clean code?

3. Bjarne Stroustrup, inventor of C++
Elegant and Efficient

4. "Reading it should make you smile the way a
well-crafted music or well-designed car
would."

5. Ratio of time spent reading vs. writing code is
well over 10:1

6. Dave Thomas
- Easy to enhance
- Has unit and acceptance tests
- Has one way of doing one thing

7. Michael Feathers
“Clean code looks like it was written by
someone who cares.”

8. Wyh U should, right clean Code.?
(bad code is just like this slide, shows carelessness)

9. 80% or more of what we do is called
Maintenance.

10. Broken windows.

11. Where to start?
Naming
Methods
Classes
Comments
Error handling

12. Naming
It should tell you why it exists, what it does, and
how it is used.
No harm in re-naming if you find better names.

13. Naming
public List<int[]> getProductList() {
List<int[]> list1 = new ArrayList<int[]>();
for (int[] x : theList)
if (x[0] == 4)
list1.add(x);
return list1;
}
public List<int[]> getFlaggedProducts() {
List<int[]> flaggedProducts = new ArrayList<int[]>();
for (int[] product: inventory)
if (product[STATUS_VALUE] == FLAGGED)
flaggedProducts .add(product);
return flaggedProducts ;
}

14. Naming
Use Pronounceable Names
genTimstmp generationTimestamp
rcrdId recordId
txtViewRltion textToViewRelation

15. Naming
Use searchable names
int realDaysPerIdealWeek = 4;
const int WORK_DAYS_PER_WEEK = 5;
int sum = 0;
for (int j=0; j < NUMBER_OF_TASKS; j++) {
int realTaskDays = taskEstimate[j] * realDaysPerIdealWeek;
int realTaskWeeks = (realdays / WORK_DAYS_PER_WEEK);
sum += realTaskWeeks;
}
for (int j=0; j<34; j++) {
s += (t[j]*4)/5;
}

16. Naming
You will probably end up surprising someone
when you rename, just like you might with any
other code improvement. Don’t let it stop you
in your tracks.
-Robert C. Martin

17. Methods
First rule: they should be small!
Second rule: they should be smaller than that!!

18. Methods
Do one thing

19. Methods
Use descriptive names

20. Methods
Use less number of arguments

21. Methods
Have no side-effects

22. Classes
Organization

23. Classes
Size

24. Classes
Single Responsibility Principle

25. Comments
Explain yourself in code

26. Error handling
Use exceptions than return codes

27. Error handling
Do not return null
Do not pass null

28. Conclusion
“Always leave the ground cleaner than you
found it.”

29. Paramvir Singh,
Senior Android Developer,
HomeShop18