Unclear Code Hurts
summary
A messy print_info function prints underscores for missing values and a bottom row of counts, forcing a rewrite and yielding zero research output; a monolithic train wrapper adds early stopping, checkpointing, weight plots, subsampling and random_state but nobody uses it; terse names like amt hs and inconsistent plurals hide business rules in mortgage code; recommendation: use linters/formatters like Black, add types and tests, and prioritise readability and naming clarity.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 8:13Story
- 14:20Mortgage application
- 21:45QA Role of Comments Documentation
- 23:20Type Annotations
- 23:53Tests
- 24:20Variable names
- 25:00Funk Tools
- 26:30Clean Code
- 27:43Clean Code Trick
- 28:28Tools
related talks
50mThe Code is Documentation Enough
12mWhy Less Code Isn’t Always Better
31mYour Research Code Works.. Until It Doesn’t: Rethinking Reproducibility
58m10 Techniques to Understand Existing Code
17mOddly Satisfying - Find delight in the mundane
45mAbstraction Considered Harmful (and other opinions about writing maintainable code)
52mThe Code is Documentation Enough
43mClean Code: Be The Hero