You Don’t Need That Design Pattern
From ArjanCodes · · 14 min

The player loads from YouTube only when you click. It uses YouTube's privacy-enhanced mode.
If the video does not play, the owner may have turned off embedding. Watch it on YouTube instead.
Description
🧱 Build software that lasts. Join the Software Design Mastery waiting list → https://arjan.codes/mastery.
Design patterns aren't bad. But using them too early can make your code more complicated than it needs to be.
In this video, I start with a Python example that uses inheritance, strategies, and a factory to solve a very small problem. Then I simplify it and explore a more realistic scenario where an abstraction actually provides value. Along the way, I look at a simple rule of thumb for deciding when a design pattern helps and when it just adds complexity.
If you've ever wondered whether you're over-engineering your code, this video is for you.
🔥 GitHub Repository: https://git.arjan.codes/2026/pattern.
🎓 ArjanCodes Courses: https://www.arjancodes.com/courses.
💬 Join my Discord server: https://discord.arjan.codes.
⌨️ Keyboard I’m using: https://amzn.to/49YM97v.
🔖 Chapters: 0:00 Intro 1:11 What’s Wrong With This? 2:14 Replace the Pattern With Functions 5:03 The Simplified Workflow 5:24 Make It More Realistic 6:40 Let the Adapter Appear Naturally 8:27 Use the Boundary in the Workflow 10:27 The Adapter Implementation 12:27 Testing the Workflow 13:25 Rule of Thumb 13:51 Final Thoughts
#arjancodes #softwaredesign #python