Which questions do you know to ask?
AI-assisted coding lets the business build its own software. They ask the right process questions, not the technical ones, and that is the easier gap to close.
Articles
Three months, 4000 commits, one architect. What working with vibe coding looks like.
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.
Code Review as a Skill: For People and for AI
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.
Different Roles, Different Review Goals
Juniors, seniors and architects look for different things in a code review. Why that mix is a strength, and why review is a dialogue.
Code Reviews: Why They Matter
The start of my code review series: what review is for, why it matters more with AI-generated code, and how other organisations approach it.
Let the Tools Do Their Job
Keep style out of code reviews. The tools I use for that: .editorconfig with dotnet format, Roslyn analyzers, ESLint, Spectral and SonarQube.
My key points for code reviews
What I check in a pull request: does it belong, can I follow it, are comments respectful, and are tests, docs and config updated with it.
Zero Warnings: Signals, Not Noise
Warnings are signals. Why I recommend a zero-warnings policy, suppress only the specific instance with a reason, and start with new code.
Applying CQRS in Practice: Lessons from a Recent Project
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.
Read More: Applying CQRS in Practice: Lessons from a Recent Project
Handling Network Failures Gracefully: More Than Timeouts and Retries
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.
Read More: Handling Network Failures Gracefully: More Than Timeouts and Retries
Unit‑Test Code Is Still Code — Apply the Same Standards
Refactor your test setup to reduce duplication and make test intent obvious. Baseline + override keeps tests readable, maintainable, and developer-friendly.
Read More: Unit‑Test Code Is Still Code — Apply the Same Standards
Why I Chose WordPress for My Personal Website (Even Though I’m a Full‑Stack Developer)
Why I picked WordPress over a custom build for my personal site: cost was a tie, so time-to-value and low maintenance decided it.
Read More: Why I Chose WordPress for My Personal Website (Even Though I’m a Full‑Stack Developer)