This blog is meant to keep a simple promise: what you read here has been checked — and someone stands behind it. So I’ll be open about how the articles are made.
The topics and the technical responsibility are mine. What gets written about, out of which practice, and with what judgment, is my call. Every article passes through my hands before it goes live.
For writing and structuring I use AI tools, Claude above all. They help with phrasing, with ordering long arguments, and with surfacing gaps. What they don’t do: make the technical decision for me. Generated text that I don’t understand and don’t verify never makes it into an article.
Every piece of SQL is run against a real database. The examples aren’t plausible-sounding snippets — they execute, typically against a fresh PostgreSQL instance in a container. Whatever doesn’t run, or returns a different result than claimed, gets fixed before it’s published.
The texts are reviewed for accuracy and partly read by a second party. A second, critical look — sometimes mine after some distance, sometimes from outside — catches what’s off or unclear.
The goal isn’t as much text as possible, but correct, verifiable content. If you spot a mistake anyway, let me know — corrections make the blog better.