How to Untangle the Worst If/Else Logic You’ve Ever Seen | Issue #83


If you’ve ever opened a function and instantly regretted it… this week’s video is for you.

I’m talking about those legendary functions: ten levels of indentation, contradictory conditions, duplicate branches, mysterious try/except blocks, and business logic so unclear that nobody knows what it actually does anymore.

I start with a really messy example and walk through the exact process I use to refactor it safely. You’ll see how to create characterization tests so you don’t break existing behavior, how to flatten deeply nested conditions with guard clauses, how to simplify and combine overlapping logic, and how to handle special cases.

Step by step, it changes into a clean, readable, and maintainable piece of Python code.


I hope this inspires you to tackle some horrible business logic next week!


Have a great weekend and enjoy the video :).

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

Have you ever written a Python script that felt slow, even though the logic was simple? Sometimes it’s not the efficiency of your code that's the problem, it’s when your code does its work. This week’s video is all about the Lazy Loading design pattern, and I think many developers underestimate how powerful (and practical) it is. I start with a real example: loading a huge CSV file that freezes your program for 10 seconds before doing anything useful. Then, step by step, we improve it using:...

If your code is hard to test, hard to reuse, and hard to change, you’re probably hardcoding your dependencies. It’s one of the most common architectural problems I see in Python code, even in production systems. In this week's video, I take a small but realistic example, a data pipeline that loads, transforms, and exports some records, and show you how Dependency Injection can turn it from a rigid mess into something clean, testable, and modular. No frameworks required. You’ll learn: Why...

Hi there, Most apps only store the final result: the current balance, the current inventory, the current status. But what if you could track every change that led to that result? That’s exactly what the event sourcing pattern allows you to do. Instead of overwriting state, you store a sequence of immutable events and derive the current state by replaying them. It’s like Git (kinda), but for your domain logic. In this week’s video, I show you how to implement event sourcing in Python from...