The document outlines principles of clean coding, emphasizing the importance of meaningful names, small functions, and clear comments for better software development. It advocates for intention-revealing names and discourages unnecessary comments, while also recommending adherence to coding standards and formatting tools. The authors, Seda Yalçın and Ömer Taşkın, highlight the need for disciplined programming practices to benefit current and future developers.

1. CLEAN WEB
SEDA YALÇIN & ÖMER TAŞKIN

2. Outline
ü About Us
ü Meaningful Names
ü Functions
ü Comments
ü Formatting
ü Questions

3. ABOUT US, ABOUT YOU?
Seda Yalçın
Software
Engineer@GG
Ömer Taşkın
Software
Engineer@GG

4. Why Clean Web?
Remembrance
Just for being in a better Web World
Just for being a better programmer
Just for next programmer
Just for us

5. What is Clean Code about?
If (((!about getting artistic points)
||
(!about being a nerd one))
&&
(about a well disciplined programmer))
{...}

6. Meaningful Names
What is meaningful name?
Small answer of the big question.
Small warning of the big danger.
Not your tongue-twister.
Not your shopping list.
Don’t be lazy or shy.
Show your intent!

7. Meaningful Names
Use intention-revealing names

8. Meaningful Names

9. Meaningful Names
VENDETTA!!!

10. Meaningful Names
Avoid disinformation

11. Meaningful Names

12. Meaningful Names
Use pronounceable &
searchable names

13. Meaningful Names
Avoid mental mapping

14. Meaningful Names
Don’t be cute
Pick One Word per Concept

15. Functions
Small

16. Functions
Do one thing
Keep it small
Blocks and Indenting

17. Functions
Function Arguments

18. Functions
Don’t repeat yourself Have No Side Effects

19. Functions
ü Don’t return null
ü Causes dirty null checks!
ü Forgotten nullchecks causes NullPointerException!

20. Functions
ü Don’t return null
ü Causes dirty null checks!
ü Forgotten nullchecks causes NullPointerException!

21. Functions
Prefer Exceptions

22. Functions
Prefer Exceptions

23. Functions
Overloading is good but!

24. Comments
Do not write comment for bad code!
Make it clean!

25. Comments
Subversion system and IDE will warn you about TODO
comment
TODO Comments

26. Comments
Journal Comments

27. Comments
Commented Out Codes
if its unnecessary; Don’t fear, delete it!

28. Comments
Noise Comment

29. Formatting
Formatting
ü You should have code standards.
ü IDE’s have formatting tool.
ü You can define special format on IDE

30. Code Smells

31. Wake Up!

32. Here we are!

33. References
Clean
Code,
A
Handbook
of
Agile
Software
Craftmanship
Robert
C.
Martin
https://class.stanford.edu/c4x/Engineering/CS144/asset/Naming.pdf