profile

The Friday Loop

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

Published 3 months ago • 2 min read

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

by ArjanCodes

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

Hey everyone, Python’s flexibility is great, but if you're working on a larger project it becomes hard to make sure not everything depends on everything else. There is a way to avoid that trap, and that's by using abstractions. Unfortunately, I often see production code with way too much coupling that can be easily improved by relying on abstractions. This week’s video shows simple abstractions using Callable, ABC, and Protocol. You’ll learn how to: Reduce unnecessary imports Decouple your...

4 days ago • 1 min read

Hey everyone, I was reviewing some of the projects I’ve worked on over the past year, and I noticed something interesting: I almost never use Python’s @dataclass anymore. Not because it’s bad. In fact, dataclasses are still a great feature of the language. But as my projects have grown more complex, especially with tools like FastAPI, Pydantic, and SQLAlchemy, I’ve found that dataclasses just… don’t fit the way I design software anymore. In my latest video, I dive into this in detail. You’ll...

11 days ago • 1 min read

Hi there, You’ve probably heard that serverless is the easiest way to deploy code to the cloud. And on the surface, it is. With Google Cloud Functions, you can literally deploy a simple Python function like this: def hello(request): return "Hello from Cloud!" A few lines of code. No servers. No infrastructure. But... there are quite a few limitations: No FastAPI or async support One route per function requirements.txt only, no pyproject.toml Cold starts for large dependencies No custom...

18 days ago • 1 min read