Completed
Write Expressive Self-Documenting Code
Class Central Classrooms beta
YouTube playlists curated by Class Central.
Classroom Contents
Twelve Ways to Make Code Suck Less
Automatically move to the next video in the Classroom when playback concludes
- 1 Intro
- 2 Why should we care about code quality?
- 3 What's Quality Code?
- 4 Schedule Time to Lower Technical Debt
- 5 What Causes Technical Debt?
- 6 Favor High Cohesion
- 7 Think about frequency of change
- 8 Favor Loose Coupling
- 9 Prefer Clear Code over Clever Code
- 10 Apply Zinsser's Principle on Writing
- 11 Write Expressive Self-Documenting Code
- 12 Avoid Long Methods-Apply SLAP
- 13 Perils of Long Methods
- 14 How long is long?
- 15 Turns out long is not about length of code, but levels of abstraction
- 16 Variable Names Represent Abstractions
- 17 Facilitating Tactical Code Reviews
- 18 Reduce State & State Mutation
