Go for Pythonistas: What You Need to Know | Issue #40


Hi there,

Python is simple but frustrating. Rust is powerful but strict. And then there’s Go—fast, modern, and surprisingly easy to use. I put it to the test against Python and Rust, and what I found blew my mind. 🤯

Go nails concurrency, has built-in tools (no pytest or flake8 needed), and in some cases… it even beats Rust in performance. Yes, really. I built a REST API, ran benchmarks, and compared everything from syntax to error handling.

Is Go the perfect balance between Python’s simplicity and Rust’s power? Watch this week’s video to find out! 🚀

Cheers,

Arjan

# News

How to Deal With Missing Data in Polars

Polars is fast and efficient, but how does it handle missing data? 🤔

A new Real Python article explores how Polars defines "missing," how it compares to Pandas, and the best ways to fill, drop, and detect null values. If you're working with data pipelines, this is a must-read! 👉 Check out here.

Top Python Libraries of 2024

Python’s ecosystem is always evolving, and staying ahead means knowing which tools are shaping the industry.

Tryolabs recently highlighted some of the most impactful Python libraries from 2024—many of which are set to play an even bigger role this year. Here are the top Python libraries in 2024. 🚀

# Community

Recently in our Discord server, an interesting discussion sparked around a video by Dave Farley about critical warning signs in software projects.

Here are a few red flags that stood out:

🚩 Rigid planning – Overplanning makes teams resistant to change, even when it’s obvious the plan isn’t working.

🚩 The “hero developer” trap – Relying on a few rock stars instead of building resilient teams.

🚩 Big risky changes – Instead of “Many More Much Smaller Steps” (MMMSS), teams often take big leaps that increase failure rates.

🚩 Strict control policies – Some teams require approval just to add a new class! This often happens in large companies with poor encapsulation, where changing one system risks breaking everything.

These discussions remind me how good software design can mitigate many of these issues. Functional programming, strong modularization, and clear feedback loops can help avoid these pitfalls.

👉 Have you ever worked in a team where even adding a class required approval? How did it impact productivity? Join the conversation in our Discord server and share your thoughts!


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

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

Most Python developers know dataclasses. Or at least… they think they do 🙂. You add @dataclass, define a few fields, and enjoy writing less boilerplate. But dataclasses hide a lot more power than most people realize and some of that power can quietly bite you if you don’t understand what’s really going on. In this week’s video, I walk through 7 lesser-known dataclass features that make your code safer, clearer, and easier to maintain. I start with common pitfalls like mutable defaults, then...

AI can write code now. But you already knew that :). If you’ve tried using AI seriously, you’ve probably noticed something: the code works (kind of) and then slowly turns into a mess. In this week’s video, I show why prompting alone isn’t enough and why software design is becoming more important, not less, in an AI-driven world. I walk through a real interaction with an AI coding assistant and show how thinking in terms of responsibilities, structure, and system boundaries completely changes...