Why Less Code Isn’t Always Better
summary
Shows a real support incident where a compact one‑line variable and one-liners cause a production StackOverflow and maxed memory, demonstrates a salary calculation collapsed into nested ternary overload that is correct but unreadable, and describes feeding a boolean check to ChatGPT which returns a terse, hard‑to‑parse version then a clearer rewrite when prompted for readability. Also reproduces a recursion rewrite that degrades from O(N) to O(2N) and breaks scalability.
AI-written summary · about
chapters (4)
related talks
20mGood Code is a Balancing Act
49mCode Golf - The Zen of Writing bad Code
01h 28mCode Golf: The zen of writing bad code II
48mRefactoring from Good to Great - A Live-Coding Odyssey
40mLessons from two decades of writing bad code
39mRead my code, or why writing readable code matters
50mThe Code is Documentation Enough
53mIntentional Code - Minimalism in a World of Dogmatic Design