Clean Code

Day 1

Introduction

Good and standardized naming

-names of packages, files, classes, voids and functions as well as variables need to have meaningful names derived from their purpose

-should be readable

-should be searchable

-consider the namespace we're generating; does it make sense?

Classes, objects and data structures

-there's a difference between objects that do something and structures that simply contain data

-when to use data structures, and why

-when to use objects, and why

-OOD and abastraction

-getters/setters and why

-better to have many small classes, with many small voids and functions

Good comments

-there are good and bad comments;

-we need to know how to generate good comments and forget about the rest

Day 2

Functions

-one thing only

-small

-arguments (good and bad)

-unintended side effects

Error handling

-when to handle errors, when to let them bubble up

-if we handle an exception, what do we do with it and why

-custom error handling classes

Code Formatting: how can we better format the code

Test-Driven Design: Open discussion of Uncle Bob's idea that programs should be TDD