Clean Coders Hate What Happens to Your Code When You Use These Enterprise Programming Tricks
summary
Argument: common enterprise habits — needless factories, verbose imports, cargo‑cult patterns, Singleton configuration and excessive comments — systematically bloat code and hide errors. Demonstrations include left-pad: 11 lines broke thousands with an ad‑hoc test harness that finds regressions; multiple FizzBuzz rewrites culminating in FizzBuzz Enterprise Edition to show over‑engineering; and a C++ refactor that replaces sprintf with safer APIs, moves declarations close to use, swaps raw pointers for smart pointers, removes a global configuration Singleton by passing typed params, and relies on constructors to fail fast — producing much simpler, working code.
AI-written summary · about
chapters (24)
- 0:00Introduction
- 1:30Enterprise Scale
- 5:40Enterprise Code
- 7:45JavaScript
- 11:13Fizzbuzz
- 13:49Python
- 15:28Fizz Buzz
- 19:04Haskell
- 24:50Comments
- 27:13A common fallacy
- 27:54Too many imports
- 29:45Awkward questions
- 30:14Peoples explanations
- 31:20The Matrix
- 32:27Too Many Inputs
- 37:26Repetition
- 38:28Factory
- 40:31Singleton
- 41:37Population explosion
- 44:46Name
- 46:34Configuration
- 49:09Disappearance
- 49:23Rename
- 52:14Noisy logging
related talks
01h 01mGuide to Destroying Codebases the Demise of Clever Code
45mC++: How Software Engineering Will Destroy Your Project?
55mIdentifying Common Code Smells (In C++)
30mDoes Your Code Hurt?
56mIdentifying Common Code Smells
59mC++ Code Smells
01h 22mSimplicity: not just for beginners
50mCore and other guidelines. The good, the bad, the... questionable?