You all know about GraphQL, right? It’s the “new” (actually not new, but things that hype recently just feel like that) hotness when it comes to data exchange through APIs on the web.

To avoid commonly made mistakes or bad design decisions and improve the overall design and effectiveness of your REST APIs, I’ve written down my personal “golden” rules when it comes to designing my REST APIs.

I’m in love. Still. And for almost 10 years already. We’ve been through thick and thin. Oh my dear Vim code editor, you never let me down, and I promise I will continue on my conversion mission for growing our beloved family, for making more people feel the absolute enlightment.

In this article you’ll learn how to create one Django settings.py file that you can use everywhere and that you don’t have to touch across runtime environments. No matter if you are targeting production, staging, development, Docker deployments or whatever: configuring your apps won’t be a factor anymore. Let’s start!

Functions in programming languages are incredibly useful: They are designed to take input parameters, do something with them, and output a result. This conforms to the well-known IPO model (Input, Process, Output). However some developers tend to interrupt that process, making it harder to follow and thus understand a function, and risking evil and nasty bugs.

Let's see why not always all roads lead to Rome.