Course Outline
Day 1
Introduction
Good and standardized naming
-Names for packages, files, classes, methods, and functions, as well as variables, must be meaningful and derived from their intended purpose.
-They should be readable.
-They should be easily searchable.
-Consider the namespace being created; does it make logical sense?
Classes, objects, and data structures
-Distinguish between objects that perform actions and structures that simply hold data.
-Understand when and why to use data structures.
-Understand when and why to use objects.
-Explore Object-Oriented Design (OOD) and abstraction.
-Explain getters/setters and their importance.
-Prefer many small classes with corresponding small methods and functions.
Effective commenting
-Distinguish between good and bad comments.
-Learn how to write valuable comments and disregard unnecessary ones.
Day 2
Functions
-Focus on doing one thing only.
-Keep them small.
-Arguments (appropriate vs. inappropriate).
-Avoid unintended side effects.
Error handling
-Determine when to handle errors and when to let them propagate.
-If you catch an exception, decide what to do with it and explain why.
-Implement custom error handling classes.
Code Formatting: Strategies for better code formatting.
Test-Driven Design: Open discussion of Uncle Bob's philosophy that programs should be developed using TDD.
Requirements
There are no specific prerequisites required to attend this course.
Testimonials (2)
The teacher addressed many relevant topics for clean coding with practical examples.
Ben van Oeveren - Movella
Course - Clean Code
I really liked that there were a lot of practical exercises in which you could put the learned immediately into action.
