Ready for Readable Code?
summary
Argues readable code saves hours: insist code communicates the actual intent, not cleverness, and adopt concrete rules like the five second rule for comprehension, one thing per file, and keeping functions under ~20 lines. Recommends an Angular style guide, uses Angular 6 and ngrx examples, and practical tools: VS Code, StackBlitz demos, the prettier formatter and the setting sync extension. Shows refactors that replace magic strings and comments with self‑describing functions.
AI-written summary · about
chapters (34)
- 0:00Intro
- 0:26Next Week
- 1:44Introduction
- 2:03Where do we spend our time
- 2:14Our little secret
- 2:38Ask Uncle Bob
- 3:03Reading Code
- 3:31Developer Behind You
- 3:49Caring
- 4:07Motivation
- 4:30Tell your boss
- 4:44Make your code easier to read
- 4:54Create a style guide
- 5:36Avoid things like this
- 5:54Hero Dispatchers
- 6:08The Cookie Rule
- 6:31Refactor
- 6:58Above the Fold
- 7:14Coding
- 8:05Less than 20 lines
- 8:29Misspells
- 8:54Writing Code
- 9:10Spelling
- 9:37Context
- 10:42Comments
- 11:28Abstracting
- 11:45Comment
- 12:01Avoid Comments
- 12:33Avoid Old Comments
- 12:47Code Never Lies
- 12:59When to Use Comments
- 14:21Dear Developers
- 14:44Tips
- 15:45Resources
related talks
26mGood Code
31mThe Importance of Clean Code
40mGood Code: What, Why, and How to Get There
19mDigging into Angular Style Guide Decisions
39mRead my code, or why writing readable code matters
39mClean, Concise, Collaborative Code
54mReadable Code: The Secret to Clean, Productive Software
20mGood Code is a Balancing Act