profile

The Friday Loop

Let’s Replace All for Loops With Map and Filter | Issue #55

Published about 2 months ago • 1 min read

Hi there,

​

Functional programming in Python can be elegant… but not always. ⚠️

​

In this week’s video, I walk through four common scenarios where replacing for loops with map() and filter() actually leads to worse code. Not just less readable—but also harder to debug, more error-prone, and sometimes even misleading.

​

We’ll dive into:

  • Exception handling that becomes a mess inside a lambda
  • Side effects (like writing to files) that violate functional principles
  • Nested logic that turns into unreadable one-liners
  • And why early exits are almost impossible with map() or filter()

​

The point? Concise code isn’t always clean code. Python gives you options—choose the one that makes your intent crystal clear. ✅

​

I hope you enjoy the video and happy coding!

​

Cheers,

Arjan

# News

🛑 Stop Writing `__init__` Methods?

Still writing __init__ methods just to set attributes? Glyph Lefkowitz says it’s time to stop—and he makes a solid case.

In this article, he explains why Python’s dataclasses often eliminate the need for custom __init__ methods, and how moving side effects elsewhere leads to cleaner, more maintainable code. 💪🧑‍💻

If you want simpler classes and fewer bugs, this is worth your time. 👉 Read the article here.​

🧠 Is Python Interpreted or Compiled?

Turns out… it’s both!

Nicole Tietz explains how Python compiles your code to bytecode before the interpreter takes over.

Understanding this duality can deepen your grasp of Python’s execution model and its implications on performance and error handling.

📖 Check out the full article here.

# Community

One of our community members, Han, shared a fantastic guide in the Discord:

“Beyond the Code: Unconventional Lessons from Empathetic Interviewing”

Whether you’re hiring or being interviewed, this piece offers fresh perspectives on making interviews more human, more relevant, and more effective.

“No matter your role, you can drive change—identify soft and hard skills, offer feedback, and help reshape the process.”

👉 Jump into the thread to read the discussion and share your thoughts!

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:

🔧 Need help with a complex codebase?

If your team is struggling with tech debt, unclear architecture, or cloud costs that keep creeping up, my team and I can help. We don’t just review, we get in and fix things. We’re only working with a few companies at a time to stay focused, so if it sounds like a fit:

​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, I love it when I come up with a design that uses exactly the things I thought were a sign of bad design. In this week's video I show you how to build a clean Python SDK for a REST API. The idea was simple: create a reusable base model that handles all the CRUD operations so you can just write User.find() and user.save(), without duplicating logic all over your codebase. Sounds great, right? Well, after recording the video, I realized something: not all APIs will have all CRUD...

5 days ago • 1 min read

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

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

19 days ago • 1 min read