Coupling 101: Design Choices That Make or Break Your Code | Issue #47


Hi there,

You’ve probably heard the phrase: “Coupling is bad.” But what if I told you that coupling is actually necessary? The real issue isn’t that your code has coupling—it’s that some types of coupling are worse than others. 🚨

In this week’s video, I dive into three real-world examples of bad coupling and show you how to refactor them into better designs. We’ll tackle:

  • Global coupling – Why global variables cause headaches and how to avoid them
  • Content coupling – When modules dig too deep into each other’s business
  • Stamp coupling – The sneaky way dependencies make your code harder to maintain

Plus, I’ll explain why AI struggles to fix these problems for you (spoiler: design is more than just code generation). 🤖❌

Happy coding and enjoy the video!

Cheers,

Arjan

# News

Python’s GIL: A Step Closer to Removal? 🐍

Big news in the Python world: the Global Interpreter Lock (GIL) might finally be on its way out! LWN’s latest article dives into PEP 703, which proposes making Python truly multi-threaded. No more GIL bottleneck—just faster, more efficient concurrency. ⚡

The catch? It’s a massive change with big implications for compatibility and performance. Curious how this could reshape Python development? 🧐 Read more here.

Duck Typing in Python: Type Less, Do More!

“If it walks like a duck and quacks like a duck…” you know the rest! 🦆 Python’s duck typing lets you write flexible, dynamic code without worrying about strict types. But when should you embrace it, and when does it become a maintenance nightmare? 🤔

Real Python’s recent course dives into duck typing, showing you how to balance flexibility and safety in your code. A must-watch for Pythonistas! 🐍💡Check it out here.

# Community

Ever used a decorator and noticed it messes with your function’s signature or docstring? 🤯 One of our Discord members ran into this exact issue when trying to preserve function metadata while decorating a method.

🛠️ What went wrong?

  • The function’s signature disappeared from tooltips in the IDE.
  • The docstring wasn’t showing as expected.
  • Even using @wraps didn’t fully resolve the issue.

👀 What’s causing it?

After some deep debugging (and a few rabbit holes 🐇), the community discovered a sneaky interaction between type hints and decorators. A small change made all the difference!

Want to know the fix? Curious if this might be affecting your decorators too? Join the discussion on Discord and see the full breakdown! 🚀


Do you enjoy my content on YouTube and would you like to dive in deeper? Check out my online courses below. They've helped thousands of developers take the next step in their careers.

🚀 The Mindset Online Course Series

The goal of this series is to help junior developers grow their skills to become senior developers faster.

💥 Other Courses

💡 If you’re part of a development team at a company, I offer special packages for companies that give your team the tools to consistently write high-quality code and dramatically increase your team's productivity.

Unsubscribe | Send 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

Hi there, Have you ever found yourself writing functions like this? def render_article(article_id, db, logger, user, config, feature_flags, etc): …and then passing the same parameters through five different layers of your app? In my latest video, I walk through a realistic Python example and show how to fix this mess using the Context Object Pattern. I’ll start with the "before" version, refactor step by step, and explore: How to group related dependencies using a context object When this...

Hi there, This week’s video is all about uv workspaces, and why they’ve completely changed the way I manage Python projects. In the video, I walk you through a real-world example: I build a CLI tool and a FastAPI API that both fetch and summarize news headlines using OpenAI. But the real lesson is in how the project is structured. I show you how to share a local package between apps, define common dependencies like openai or httpx only once. And you can manage everything using uv’s workspace...

Hi there, When I see an if-statement with multiple elifs in my code, it almost always triggers an investigation. Is there some way to rewrite this to make the logic simpler? Is there a chance that in the future I'll need to add even more complexity? If so, I'll try to redesign the code so that I don't need that chain of if-elif statements. In this week’s video, I cover a design pattern that helped me eliminate many of those chains from a project + at the same time made the code easier to...