In early 2026, I was part of a small team that built Cockpit — a management tool that helps organisations stay on top of their own design choices, roles, and priorities for transitio.nl. René had spent fifteen years developing the…
Why Review Still Matters — and What Changes When Code Is AI-Generated This article is part of my code review series. It focuses on a question that’s become more relevant with the rise of tools like GitHub Copilot, ChatGPT, and…
Why Code Review Means Something Different to Everyone — And Why That’s a Strength This article is part of my code review series. It focuses on why code review means something different to everyone — and why that’s a strength.…
My Personal Toolbox for Code Consistency and Clean Reviews This article is part of my code review series. It focuses on one of the most underused productivity boosters: automated checks for style and structure. In the early days, a lot…
This article is part of my code review series. It focuses on the key areas I personally pay attention to when reviewing code — across roles, projects, and even AI-generated changes. Reviewing code isn’t just about catching bugs. It’s about…
Warnings are not errors — but they exist for a reason. Whether they come from the compiler, analyzers, or external tools, a warning is a signal that something may be wrong or unclear — even if the code compiles just…
Introduction Over the years, I’ve reviewed a lot of code — from junior developers’ first PRs to AI-generated bug fixes. I’ve seen code reviews save weeks of future debugging, and I’ve seen them miss the one line that caused a…
Most systems rely only on timeouts and basic retries, but that's rarely enough.
Resilience patterns like circuit breakers and concurrency limits help systems fail gracefully instead of collapsing under pressure.
We applied a pragmatic CQRS pattern using separately deployable command and query components with a shared database. GraphQL provided flexible querying, but required discipline and careful schema management to remain effective at scale.
Refactor your test setup to reduce duplication and make test intent obvious.
Baseline + override keeps tests readable, maintainable, and developer-friendly.