10 Tips to Keep Your Software Simple | Issue #49


Hi there,

Ever looked at your old code and felt secondhand embarrassment? Yeah, me too.

Keeping your code simple and maintainable is an art.

In today’s video, I break down 10 essential tips that will help you write cleaner, more efficient Python code. 🚀

Some key takeaways:

🛑 Stop overengineering—simple solutions are often the best.

✂️ Cut the copy-paste habit—DRY code is maintainable code.

🧹 Refactor before your code turns into a horror movie.

Happy coding! 🐍

Cheers,

Arjan

# News

How Do Terminals Really Work?

Ever wondered why your terminal behaves the way it does? Julia Evans breaks it down in this fantastic article on terminal rules—the unwritten conventions that shape how terminals interpret input, handle output, and interact with programs. 💻

Learn about control characters, line discipline, and how different tools (like SSH) affect terminal behavior. If you’ve ever been surprised by how a command behaves, this post will help you understand what’s really happening under the hood. 📖 Read more here!

🚦 The Boolean Trap: When True/False Isn’t Enough

Booleans are simple, right? True or False, nothing in between. But in software design, relying too much on booleans can lead to rigid, unclear, and hard-to-extend code.

🛠️ This article explores why booleans can be a trap, when to replace them with richer data types, and how to write more expressive, maintainable code. If you’ve ever had a function with multiple if statements checking flags, this one’s for you! Click here to check it out.

# Community

One of our ArjanCodes Discord members, Niklas, is working on a bachelor thesis about music recommendations and album covers. He’s exploring a fascinating question:

💡 Can the visuals of an album cover influence how we perceive and choose music? 🎵🎨

To get statistically significant results, he needs 150+ people to take a quick survey where you listen to short music clips and swipe left or right based on your preferences.

If you want to help him out, check out the thread here or join the discussion on the ArjanCodes Discord to 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

Jan van Eijklaan 2-4, Bilthoven, UT 3723 BC

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

Hi there, Have you ever hesitated before hitting git merge or git rebase because… well, who actually understands Git? 🤯 Good news! In this week’s video, I walk through a real-world FastAPI project and show exactly how to merge, fast-forward, and rebase—step by step. No fluff, just practical Git skills you’ll actually use. Plus, I’m sharing some advanced Git tricks to make your workflow smoother. Happy coding and enjoy the video! Cheers, Arjan # News Build TUI Apps with Python’s Textual Ever...

Hi there, You’ve probably heard the phrase: “Coupling is bad.” But what if I told you that coupling is actually necessary? The real issue isn’t that your code has coupling—it’s that some types of coupling are worse than others. 🚨 In this week’s video, I dive into three real-world examples of bad coupling and show you how to refactor them into better designs. We’ll tackle: Global coupling – Why global variables cause headaches and how to avoid them Content coupling – When modules dig too deep...

Hi there, Ever had a function work most of the time but randomly break when you least expect it? That’s a sign your code is brittle. And brittle code means debugging nightmares. The good news? You can avoid this! In this week’s video, I break down: 🔹 Why checking types at runtime is a bad idea 🔹 The best way to handle value constraints without making a mess 🔹 Whether your function should return None or raise an exception 🔹 Why failing fast is the best approach to writing reliable Python And...