Frequently Asked Questions

Who writes this?

A small team with production C++ experience. We select the topics, design the investigations, verify the results, and make the editorial calls. We use AI tools extensively in our workflow — for research, drafting, and editing — the same way most technical writers now use Copilot, ChatGPT, or Grammarly. The judgment is human. The typos are fewer.

Are the benchmarks real?

Yes. Every performance number comes from code that compiled and ran on real hardware. We report the CPU, compiler version, and flags for every measurement. If a number looks surprising, that's usually why we wrote the article.

Can I reproduce your results?

The code examples in every article are complete and compilable. For benchmark-heavy articles, we specify the exact compiler versions and flags used. Hardware matters — results on your Zen 5 may differ from our Haswell numbers, and that's part of the point.

Do you use AI tools?

Yes, and we don't pretend otherwise. AI assists with research, drafting, and editing. But every technical claim goes through verification — benchmarks run in containers, assembly output gets checked against real compilers, and code examples must compile. We don't publish numbers we haven't measured or claims we haven't verified. The tooling accelerates the process; it doesn't replace the engineering judgment.

Why no ads?

Ads misalign incentives. They reward pageviews, not quality. We'd rather write one thorough article per week than five clickbait listicles per day. Revenue comes from courses and sponsorships that are relevant to the audience — not from tracking you across the web.

Why no cookie banner?

Because we don't use cookies. No tracking scripts, no analytics pixels, no third-party anything in your browser. The theme toggle uses localStorage. That's it.

I found an error

Please tell us. Technical accuracy is the whole point. Open an issue on GitHub and we'll fix it or explain why we disagree.

Can I write for you?

We're not open to guest posts right now, but we're always interested in hearing from practitioners with war stories. If you've measured something surprising, reach out via GitHub.