The Art of Clean Code
summary
Claims practical rules: name things by domain so use domain names like Customer.firstName, avoid abbreviations, drop useless interfaces and keep APIs small, and rename code freely when a better name appears. Enforce parameter and null checks at layer boundaries, prefer Option/Optional or exceptions over sentinel return values, and place constants in the class that uses them. The session reports distilled heuristics from repeated training runs (10+ times) and demonstrates these rules on Java examples.
AI-written summary · about
chapters (14)
- 0:00Start
- 2:14Why Clean Code?
- 9:46Name Length
- 16:15Act Professional
- 16:59Function Signature (2)
- 25:00Extract Method Object refactor
- 26:26Side Effects
- 27:00Temporal Coupling
- 27:57Basic Shape
- 29:10Data Structures struct
- 34:48Feature Envy
- 35:56Code Formatting
- 41:10Code Expressiveness
- 42:25Bad Comments
