Why “Clean Code” Often Creates Worse Designs
→ Get started with Hostinger today: http://hostinger.com/arjancodes (make sure to use coupon ARJANCODES).
In this video, I refactor a small Python program that looks clean on the surface but hides a messy design underneath. Step by step, I remove unnecessary abstractions and restructure the program around cohesion and clear behavior instead of tiny components.
🔥 GitHub Repository: https://git.arjan.codes/2026/clean.
🎓 ArjanCodes Courses: https://www.arjancodes.com/courses.
💬 Join my Discord server: https://discord.arjan.codes.
⌨️ Keyboard I’m using: https://amzn.to/49YM97v.
🔖 Chapter…
Watch on YouTube ↗
(saves to browser)
Chapters (12)
Intro
0:52
What People Mean by “Clean Code” (And Where It Goes Wrong)
1:27
BEFORE: “Clean” Interface, Messy Reality
3:25
Hostinger Sponsored Integration
4:56
Step 1: Delete the Fake Abstraction and Container
5:54
Step 2: Introduce ReportConfig
10:17
Step 3: Make the Pipeline Explicit: Load → Summarize → Export
13:16
Step 4: Model the Result as a Cohesive Object
18:30
Step 5: Move Business Rules Into One Readable Place (is_valid)
21:31
Show the Final “After” Code (Your Version)
25:13
Reframe “Clean” as Cohesion, Not Smallness
25:52
Final Thoughts
DeepCamp AI