My role as architect on a vibe-coded project with 4,000+ commits in under three months: an AI review bot, defence in depth and release reviews.
Read More: Three months, 4000 commits, one architect. What working with vibe coding looks like.
AI can write code, but review still decides whether it does the right thing. What changes when the author is a model, and why tests matter more.
Juniors, seniors and architects look for different things in a code review. Why that mix is a strength, and why review is a dialogue.
From developer to architect, I've learned that most answers depend on context.
I am Patrick Verbeeten, I’ve started as a developer with zero experience and a lot to learn. Over the years, I’ve worked on a wide range of projects—across domains, teams, and technologies. That variety shaped how I think about software: not just how to build it, but how to adapt it, scale it, and help others do the same.
Today, my focus is on software architecture and cloud systems—and mentoring others through the complexity. I’ve built enough to know that best practices don’t exist in isolation. Every decision has a trade-off, and the value lies in understanding why something works (or doesn’t).
I write to share that perspective—not to prescribe solutions, but to help others navigate the same choices with clarity and confidence. If what I write helps someone avoid a mistake, rethink a pattern, or explain their reasoning to a colleague more effectively—then it’s worth it.
I’m always happy to talk about software, architecture, or team challenges. Let’s start a conversation.
Contact