Latest Posts

More and more software projects are moving to an event-driven architecture. The biggest reason is maintainability, and let me tell you, they are right. Monolithic architectures are not maintainable if you work in a team of over 20 software engineers. Full stop

One of the ways to set up an event-driven architecture, and also the most preferred one, is Kafka. Kafka is an open-source project from the Apache Foundation. In its essence, it is a distributed log, enabling you to produce and consume messages from topics. We could explore Kafka’s theory further, but I’m not the best person to teach it, since there are books that already do a good job of explaining it.

The goal of DevOps is to create an environment where developers can quickly push changes to production. This is the core idea, and while it may seem simple, many mistakes are made in relation to DevOps.

Today we will discuss the eight most common errors that people make when building a DevOps pipeline.

Alright, ladies and gentlemen, today is hands-on. We will learn how to set up a CI/CD pipeline using GitLab and deploy a sample application to AWS with short-term credentials. This is the absolute best practice, so if you’ve ever wondered how CI/CD pipelines work between a version control system and a cloud provider, now is your chance to learn.

Our agenda today consists of three simple steps.

Generative AI is the big tech story of the decade, that much is clear. While AI has existed since the 1960s, we’ve seen several AI winters, where research and usage dropped off. This changed when ChatGPT was first released. Since then, not only has everyone kept talking about AI, but everyone has also been using it.

The reap of real benefits from artificial neural networks started with this release. And even though we don’t even fully understand why ChatGPT works the way it does (which we’ll discuss soon), it does work. But there’s a key point many people overlook:

Instagram, Twitter, LinkedIn, Facebook… social media is all around us. And even though we have lived with it for years already, it seems like we don’t know how to use it in the “correct” way yet.

Think about it: how much did you spend on social media in your lifetime? And how much of that time did you actually want to spend time on social media?

We are not talking minutes or hours; we are talking days. And it keeps getting worse.

Websites are the core of every business and public figure. Whatever you are doing, if you want to look credible in front of your customers, you are going to need a website that represents you. And thanks to today’s technology, it is easier than ever to build a static website.

In the following article, we will take a look at how we can build a website in the most efficient way possible. The goal is to cut the time commitment while maintaining high quality. You won’t need any knowledge at all, since we will build the website completely with AI. In other words, this is a step-by-step tutorial for vibe coding your website without any knowledge of how HTML, CSS, or JavaScript works. So without further ado, let’s get started!

Welcome to the third and final part of my Identity and Access Management (IAM) trilogy. In the last two parts, we defined what authentication and authorization are. We also discussed two very important protocols for managing authentication and authorization via third-party apps like OAuth 2.0 and OpenID Connect.

This covers most of the key aspects of authentication and authorization. However, there is still one important puzzle piece missing, and that is persisting a session after a user logs in.

Welcome to the second part of the Identity and Access Management (IAM) trilogy. Today, we will explore the best practices for two key protocols: OAuth 2.0 and OpenID Connect (OIDC). The two protocols are very like each other, but still complex on a technical level. Many of you have used one or the other at some point.

There are a lot of tutorials about this topic, especially OAuth. But a lot of them contain a lot of jargon and false information. There are two reasons for this. First, authentication and authorization are themselves complex topics. They require a lot of background information to even begin with. Second, the protocols have a lot of different ways for implementation. This makes it hard to deliver a good tutorial that covers most aspects of the technology. I wanted this article to be clear and accurate for software developers and beginners. So if you work in or around tech, this article is for you.

Welcome to the first part of my short trilogy about the topic of identity and access management (IAM). In this series, we’ll look at the best ways to manage users. We’ll also discuss how to handle secure user sessions in today’s IT world.

The first part gives an overview. It covers authentication and authorization. You will gain the fundamental knowledge required for the more complex topics.

The second part will be about how the workflow looks for authorizing users. We’ll look at how to enable secure user authorization. We’ll use standards like OAuth and OpenID Connect (OIDC). Passkeys will also be a very interesting topic here, so stay tuned.

At one point or another, every developer will have to set up their workspace on a completely new machine. The reason could be anything, but what is certain is that this day will come sooner or later. And when it comes, be sure to have prepared for it so it doesn’t take you days, but hours at most.

How do we prepare for it? Well, the biggest workload when setting up a workspace is configuration. It takes time to set up partitions or install mandatory applications. But the biggest gotcha is configuring your applications to fit your needs. Be it a simple VS Code config file or a complete Neovim IDE, it does not get better the longer you work in this field.