Eight years after the release of JUnit 5, the time has finally come: JUnit 6 is here.

For many it is probably already old hat or rather everyday life.

Anyone who has ever worked with Terraform or CloudFormation knows the game: you struggle with state locks, drifting resources and a DSL (Domain Specific Language) that often feels more like configuration than real code.

Jujutsu (jj): A new paradigm for version management Git is the industry standard, no question.

While REST often provides too much data (overfetching) or gRPC is too complex to handle for web clients, GraphQL has established itself as the standard for flexible front ends.

In recent years, anyone who wanted to use gRPC with Spring Boot often had to resort to community starters.

Git is one of those tools that people often think of as “finished.

Anyone who has ever scaled an infrastructure across multiple AWS accounts using pure Terraform knows the problem: you copy the same provider block and the same backend configuration for the tenth time.

When we currently talk about the Model Context Protocol (MCP), TypeScript or Python usually dominates the timeline.

Git is a team sport: Why we need strategies When you start working on your first projects, Git is usually pretty simple: you write code, do a git add, then a git commit and finally a git push.