Questions, feedback, or a correction?
Clear technical writing improves when readers challenge it. Contact Paul about an article, a correction, or Golang Tutorial itself.
For corrections, include the article URL, the affected section, and enough detail to reproduce the issue. Do not send passwords, API keys, private source code, or other secrets.
Response priorities
Technical inaccuracies and broken examples receive priority. General questions and partnership inquiries may take longer.