Contact

The fastest way to reach us is email:

What's worth sending

Corrections of any kind: typos, broken code examples, output that doesn't match what we said it would, a function we described that doesn't exist anymore. Even a one-line "this snippet on /guides/foo doesn't compile" is useful, and it's how the site gets less wrong over time.

Suggestions for topics we haven't covered yet. We can't promise to write any specific guide, but the backlog gets shaped by what people ask for.

Privacy and legal questions. If the privacy policy or terms of service are what brought you here, say so up front and we'll prioritize the reply.

What we don't accept

No guest posts, no sponsored content, no paid link insertions, no "content partnerships". The answer is no, and we won't reply to follow-up emails on those.

Security reports

If you've found a security issue with the site itself (not with a code example), email the same address with "security" in the subject line and we'll respond quickly.

Reply times

One person reads the inbox. We read every message but can't always write back, especially for general feedback. Corrections and legal questions get priority and usually a same-week reply.