profile

The Friday Loop

The New Python 3.13 Is FINALLY Here! | Issue #22

Published over 1 year ago • 2 min read

Hi there,
​

Python 3.13 is officially here, packed with some seriously exciting upgrades! 🐍
​

The headline feature? Disabling the GIL (yep, you read that right) is a game changer for multithreaded applications. Plus, the interactive interpreter now has full color support 🎨, making debugging and experimentation even more intuitive.
​

But that’s just the tip of the iceberg. In this week’s video, I’ll walk you through all the major updates, including:
​

  • A boost to garbage collection for faster memory management ⚡
  • Improvements to package and module handling 📦
  • Some experimental (but very promising) JIT optimizations for performance 🚀
    ​

P.S. And yes, Python 3.14 is just around the corner… should we start calling it Pi-thon? 🍰
​
Enjoy the video and happy coding!

Cheers,

Arjan

# News

It’s Time to Stop Using Python 3.8

With the release of Python 3.13, it’s the perfect time to consider upgrading—especially if you haven’t been keeping up with recent versions.

If you’re still using Python 3.8, you could be missing out on essential improvements in performance, security, and new features. This article dives into the key reasons to move on from 3.8, outlining the risks of staying on an outdated version and the benefits of upgrading. Read the full article here.

Goodhart's Law in Software Engineering

Ever heard of Goodhart’s Law? It’s more relevant to software engineering than you think! 🤔

Goodhart’s Law states, “When a measure becomes a target, it ceases to be a good measure.” This insightful article explores how this principle plays out in software engineering, from productivity metrics to code quality—and why focusing too much on the wrong targets can lead to unintended consequences. Curious to learn more? Read the full article here.

# Community

Last month, we welcomed 242 new members to the Discord community! I couldn’t be more thrilled to have you all here. A huge thank you to everyone for your amazing contributions to the discussions so far.

If you’re new, don’t forget to pop into the #😎introduce_yourself channel and say hi! 👋 And if you haven’t joined yet, there’s no better time. Click the link below and be part of our growing community:👉 Join ArjanCodes on Discord​

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.

🪄 Learntail

My team and I created an AI quiz generator designed to accelerate your learning, called Learntail. You can try it for free or unlock even more capabilities and features with the monthly subscription. Take a look here.

​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

Have you ever hesitated between writing a method or a property, and then just picked one because “it felt right”? That small choice actually carries a lot of design weight. In this week’s video, I explore when properties make sense and when methods are the better choice. I talk about what properties promise to the reader of your code, why setters should be used carefully, how this choice affects abstractions and Protocols, and where async fits into all of this. This video is also a good...

13 days ago • 1 min read

Most systems don’t start out needing CQRS. They start simple: create, update, list, dashboard. Everything in one place. Everything reasonable. Until read requirements slowly begin to reshape the system, often in subtle ways 🧩. In this week’s video, I show how that happens using a FastAPI app backed by MongoDB, and how Command Query Responsibility Segregation (CQRS) provides a clean way out once reads and writes want very different things. Along the way, I cover: separating command intent from...

20 days ago • 1 min read

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,...

27 days ago • 1 min read