DuckDB: SQL and DataFrames Just Got Married | Issue #39


Hi there,

Ever wish you could combine the simplicity of SQL with the flexibility of DataFrames? Meet DuckDB—a tiny, analytics-focused database that works wonders for anyone wrangling data. 🦆✨

In this week’s video, I explore:

  • Why DuckDB is perfect for analytical workloads
  • How it seamlessly integrates with tools like Pandas
  • The difference between in-memory and persistent storage

If you’re tired of clunky workflows and want a lightweight, powerful solution, this is a tool you need to see in action. 🚀

Cheers,

Arjan

# News

Burnout: It's Not Just About Overworking! 🔥

Matheus Lima’s article, completely reshaped my understanding of burnout. It’s not just about working long hours — it’s about how we work, the systems we navigate, and the expectations we carry.

The piece dives into the real drivers of burnout, like mismatched priorities, lack of control, and the relentless pressure to “do more with less.” 🚨 It’s a wake-up call to rethink not only workplace culture but also our personal boundaries and habits.

It’s a refreshing, empowering perspective for anyone feeling overwhelmed in today’s fast-paced world. 👉 Read the full article here.

Secure Coding Practices in Agile Development

Integrating secure coding practices into agile development doesn’t have to be a headache. 🤯

This article breaks it down with actionable advice—like kicking off security efforts early, leveraging automated tools to spot vulnerabilities fast, and turning security into a collaborative, iterative part of your workflow. ✨ Check it out here.

# Community

Gabe, a member of the ArjanCodes Discord, was struggling to debug a Flask app in VSCode. No matter what they tried, the usual step-by-step debugging wouldn’t work. Why? Flask behaves differently, and the solution wasn’t as straightforward as expected.

That’s when the community stepped in with insights that completely changed the approach. From a better way to track variables to a key tweak in the Flask setup, the discussion led to a breakthrough.

Curious how Gabe finally solved it? Join the conversation in Discord and see for yourself! 🚀! 🎉


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