I fixed the code and made it worse | Issue #86


In a recent video on refactoring complicated business logic, I managed to introduce several subtle errors. Many of you immediately spotted them in the comments. That’s exactly what my first video in 2026 is about.

I walk through the mistakes I made, explain why they happened, and show how easy it is to accidentally change behavior when you refactor code. Even with tests in place and decent coverage, assumptions can sneak in, business rules can shift, and logic can quietly break without anyone noticing.

This video is also about something broader: there often is no single ground truth in business logic. Not the original code, not the refactored version, not the tests, and not even the requirements. As developers, we constantly translate vague, changing reality into deterministic code. And that’s where many of these mistakes come from.

I hope you enjoy the video, and I want to wish you a great 2026, with lots of learning, curiosity, and healthy skepticism (keep it coming!).

Cheers,

Arjan


Do you enjoy my content on YouTube and would you like to dive in deeper?

🚀 Check out my online courses

My courses have helped thousands of developers take the next step in their careers. Check out these courses to help grow your skills and become a senior developer:

👕 Clean code and clean clothes

The ArjanCodes merch store features T-shirts, hoodies, hats, and more for the clean-code-obsessed. Careful though: you'll look dangerously professional while reviewing PRs.

👉 Check out the store here and grab something before your stand-up call starts.

Unsubscribe | Sent by ArjanCodes

Wolvenplein 25, Utrecht, UT 3512 CK

The Friday Loop

Every Friday, you'll get a recap of the most important and exciting Python and coding news. The Friday Loop also keeps everyone posted on new ArjanCodes courses and any limited offers coming up.

Read more from The Friday Loop

Code can be correct and still be unpleasant to read. A lot of software design isn’t about what the code does but about how clearly it communicates the sequence of ideas behind it. In this week’s video, I explore the Fluent Interface pattern by refactoring a small animation engine in Python. I start with a clunky but functional API, then gradually reshape it until defining an animation reads almost like a sentence: move, rotate, scale, fade. Enjoy this deep dive into API design, readability,...

Have you ever looked at a Python script and thought: “Why is this slow? The logic is trivial.” Very often, the problem isn’t what your code does, but how often it does expensive work. In this week’s video, I start with a deliberately inefficient example: parsing a large CSV file multiple times. From there, I use it as a vehicle to introduce 10 powerful Python features that many developers either don’t know about or don’t know when to apply. I look at things like: • caching expensive...

I almost didn’t publish this week’s video. It’s about the Specification design pattern, and if I’m honest, the final version of the code scared me a little. It’s complex, abstract, and in many cases… absolutely overengineered. But there’s a reason I still decided to share it. In the video, I explore how the Specification pattern tackles a very real problem: business rules duplicated across different parts of a system, slowly drifting apart and becoming harder to change safely. Is this...