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. Complete. You are the only author and the main branch belongs solely to you.

Hello everyone, I actually thought the whole time I had already written an article about this. Then I realized that although I’ve already mentioned ArchUnit a few times, but I haven’t written anything about it, except in my Obsidian Vault. So I’ll catch up on that today.

Why We Hate Code Reviews (and Why It’s Wrong)

The code is written, the unit tests are green, and you are proud of your solution. You create the pull request (PR), push it into the team channel and move on to the next task.