10 Tips to Become REALLY Good at Python | Issue #37


Hi there,

Let’s talk about Python—the language we all love. ❤️ You might think you know your way around it, but even senior developers can fall into common traps or miss out on some of its best features.

In this week’s video, I break down 10 tips that will make your code cleaner, faster, and more Pythonic.

For example, comprehensions are not just for lists—you can use them for sets, dictionaries, and even generators. And if you’re not using f-strings yet… well, you’re missing out on a lot of readability and power!

The last tip, though, is my personal favorite—it’s one I wish more developers knew when I review their code.

Cheers,

Arjan

# News

Generative AI Is Not Going to Build Your Team

Generative AI tools like ChatGPT and GitHub Copilot can supercharge productivity, but let’s be real—they won’t replace the creativity, collaboration, or critical thinking of a skilled engineering team. 🚀

As this Stack Overflow article points out, AI can’t handle complex team dynamics or bring that essential human touch to innovation. Think of AI as your assistant, not your substitute—a powerful sidekick that helps you level up, not take over. Read the full article here.

Insane and Fun Facts About SQLite

SQLite is the most widely deployed database engine in the world, powering over a trillion active databases. It stands out from most software by being in the public domain, allowing unrestricted use.

But there’s more to its story—SQLite operates under a unique Code of Ethics inspired by The Rule of St. Benedict, bringing a refreshing perspective to software development. ✨

Want to uncover more cool facts and dive into SQLite’s fascinating journey? 👉Click here to learn more.

# Community

In our Discord community, an interesting discussion unfolded about preserving function signatures and docstrings when using Python decorators. 🤔 One member shared their challenge of losing these critical details, sparking a deep dive into solutions like functools.wraps, advanced type hints with ParamSpec, and even IDE-specific quirks. 🛠️

Curious about how it turned out or want to join discussions like this? ArjanCodes’ Discord is the place to connect, learn, and grow as a programmer. 🌟


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

In a recent video on refactoring complicated business logic, I managed to introduce several subtle errors. Many of you immediately spotted them in the comments. That’s exactly what my first video in 2026 is about. I walk through the mistakes I made, explain why they happened, and show how easy it is to accidentally change behavior when you refactor code. Even with tests in place and decent coverage, assumptions can sneak in, business rules can shift, and logic can quietly break without anyone...

You’ve tested the endpoint. The response looks right. No errors in the terminal. So you’re done, right? Well... not quite. In the last video of this year (time flies!) I start with a tiny FastAPI app that "works", and step by step, I turn it into something that’s actually ready for production (and that's more work than you think). That includes: Proper type usage Input validation and error handling Configuration management Rate limiting to prevent abuse ...and more! All using a real example:...

Sometimes your code fails, you change absolutely nothing, and on the next run everything works again. If that sounds familiar, this week’s video is for you. These kinds of failures usually have nothing to do with bad code. They come from the outside world: APIs that time out, networks that briefly misbehave, or LLMs that occasionally return something almost structured, but not quite. It’s frustrating, because the failure feels random, and those types of failures are really annoying to debug!...