Ridiculous Ways to Define Functions in Python | Issue #56


Hi there,

We all use def to define functions in Python. But did you know there are at least 7 other ways to do it? Some of them are useful. Some are questionable. And the last one is so ridiculous, it might crash your interpreter.

In this week’s video, I walk through each method, explain how it works, why you should use it (or not), and what it teaches us about how Python works under the hood.

This was a really interesting topic to explore. I learned a lot from it and I hope you will too.

Happy coding!

Cheers,

Arjan

# News

It’s My Birthday Week! 🎉

That’s right: I’m officially getting deprecated… but still fully functional! On June 8th, I’m turning 48, and to celebrate another year under the sun, I’m giving you a special gift: 20% off all ArjanCodes courses (excluding the Professional version).

It’s the perfect performance boost for your coding skills.

To claim your 20% discount, use coupon code BIRTHDAY2025 at checkout. This offer is available until June 8th at midnight!

Debugging f-strings Is Fun

Here’s something weird I came across this week. Your str(obj) call works just fine… but plug that same object into an f-string and boom — you get a TypeError.

Turns out, f-strings don't use str() under the hood — they use format(). And in some edge cases (like with proxy objects or sandboxed environments), that subtle difference matters.

Brandon Chinn wrote a great deep dive on this exact problem. Check it out here.

It’s a great reminder that Python is usually friendly, until it’s not.

# Community

How Do You Learn Software Architecture?

This week someone asked a great question in my Discord server: “I can write code, but how do I get better at designing it?”

That kicked off a really thoughtful thread about learning architecture step by step, dealing with anxiety while coding, and figuring out how to make your code easier to change later. A few great book recommendations came up too.

If you ever feel stuck trying to structure your code or scale your skills, you’re not alone, and the Discord is a great place to talk about it.

👉 Join the community now 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

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

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

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