# Rules

## 1. Be friendly and welcoming.

Post is not in keeping with an inclusive and friendly technical atmosphere.

## 2. Be patient.

Remember that people have varying communication styles and that not everyone is using their native language. (Meaning and tone can be lost in translation.)

## 3. Be thoughtful.

Productive communication requires effort. Think about how your words will be interpreted. Remember that sometimes it is best to refrain entirely from commenting.

## 4. Be respectful.

In particular, respect differences of opinion.

## 5. Be charitable.

Interpret the arguments of others in good faith, do not seek to disagree. When we do disagree, try to understand why.

## 6. Be constructive.

Avoid derailing: stay on topic; if you want to talk about something else, start a new conversation. Avoid unconstructive criticism: don't merely decry the current state of affairs; offer—or at least solicit—suggestions as to how things may be improved. Avoid snarking (pithy, unproductive, sniping comments) Avoid discussing potentially offensive or sensitive issues; this all too often leads to unnecessary conflict. Avoid microaggressions

## 7. Be responsible.

What you say and do matters. Take responsibility for your words and actions, including their consequences, whether intended or otherwise.

## 8. Follow the Go Code of Conduct

As a part of the Go community, this subreddit and those who post on it should follow the tenets laid out in the Go Code of Conduct: https://golang.org/conduct

Treat everyone with respect and kindness. Be thoughtful in how you communicate. Don’t be destructive or inflammatory.

## 9. Must be Go Related

Posts must be of interest to Go developers and related to the Go language.

This includes: - Articles about the language itself - Announcements & articles about open source Go libraries or applications - Dev tools (open source or not) specifically targeted at Go developers

We ask that you not post about closed-source / paid software that is not specifically aimed at Go developers in particular (as opposed to all developers), even if it is written in Go.

## 10. Do Not Post Pirated Material

Do not post links to or instructions on how to get pirated copies of copyrighted material.

## 11. Job Posts Go in the "Who's Hiring?" Post

We have a monthly "Who's Hiring?" post that will stay pinned to the top of the subreddit. To avoid too much noise from companies, please post job openings there. Please keep in mind, this is for 1st party postings only. No 3rd party recruiters.

## 12. No GPT-generated or GPT-quality content.

No GPT or other AI-generated content is allowed as posts, post targets, or comments. This is only for the content itself; posts about GPT or AI related to Go are fine.

As GPT content is difficult to distinguish from merely low-quality content, low-quality content may be removed too. This includes but is not limited to listicles and "Go tutorials" that have no human voice and add nothing of their own.

# Documentation

* [Official Go Documentation](http://go.dev/doc)
* [Standard Library Docs](http://pkg.go.dev/std)
* [Other Package Docs](http://pkg.go.dev)

# Community

* [Go Nuts Mailing List](http://groups.google.com/group/golang-nuts)
* [Go questions in Stackoverflow](http://stackoverflow.com/questions/tagged/go)
* [Resources for new Go programmers](http://dave.cheney.net/resources-for-new-go-programmers)

<div class="md"><h1>Rules</h1>

<h2>1. Be friendly and welcoming.</h2>

<p>Post is not in keeping with an inclusive and friendly technical atmosphere.</p>

<h2>2. Be patient.</h2>

<p>Remember that people have varying communication styles and that not everyone is using their native language. (Meaning and tone can be lost in translation.)</p>

<h2>3. Be thoughtful.</h2>

<p>Productive communication requires effort. Think about how your words will be interpreted. Remember that sometimes it is best to refrain entirely from commenting.</p>

<h2>4. Be respectful.</h2>

<p>In particular, respect differences of opinion.</p>

<h2>5. Be charitable.</h2>

<p>Interpret the arguments of others in good faith, do not seek to disagree. When we do disagree, try to understand why.</p>

<h2>6. Be constructive.</h2>

<p>Avoid derailing: stay on topic; if you want to talk about something else, start a new conversation. Avoid unconstructive criticism: don&#39;t merely decry the current state of affairs; offer—or at least solicit—suggestions as to how things may be improved. Avoid snarking (pithy, unproductive, sniping comments) Avoid discussing potentially offensive or sensitive issues; this all too often leads to unnecessary conflict. Avoid microaggressions</p>

<h2>7. Be responsible.</h2>

<p>What you say and do matters. Take responsibility for your words and actions, including their consequences, whether intended or otherwise.</p>

<h2>8. Follow the Go Code of Conduct</h2>

<p>As a part of the Go community, this subreddit and those who post on it should follow the tenets laid out in the Go Code of Conduct: <a href="https://golang.org/conduct">https://golang.org/conduct</a></p>

<p>Treat everyone with respect and kindness. Be thoughtful in how you communicate. Don’t be destructive or inflammatory.</p>

<h2>9. Must be Go Related</h2>

<p>Posts must be of interest to Go developers and related to the Go language.</p>

<p>This includes: - Articles about the language itself - Announcements &amp; articles about open source Go libraries or applications - Dev tools (open source or not) specifically targeted at Go developers</p>

<p>We ask that you not post about closed-source / paid software that is not specifically aimed at Go developers in particular (as opposed to all developers), even if it is written in Go.</p>

<h2>10. Do Not Post Pirated Material</h2>

<p>Do not post links to or instructions on how to get pirated copies of copyrighted material.</p>

<h2>11. Job Posts Go in the &quot;Who&#39;s Hiring?&quot; Post</h2>

<p>We have a monthly &quot;Who&#39;s Hiring?&quot; post that will stay pinned to the top of the subreddit. To avoid too much noise from companies, please post job openings there. Please keep in mind, this is for 1st party postings only. No 3rd party recruiters.</p>

<h2>12. No GPT-generated or GPT-quality content.</h2>

<p>No GPT or other AI-generated content is allowed as posts, post targets, or comments. This is only for the content itself; posts about GPT or AI related to Go are fine.</p>

<p>As GPT content is difficult to distinguish from merely low-quality content, low-quality content may be removed too. This includes but is not limited to listicles and &quot;Go tutorials&quot; that have no human voice and add nothing of their own.</p>

<h1>Documentation</h1>

<ul>
<li><a href="http://go.dev/doc">Official Go Documentation</a></li>
<li><a href="http://pkg.go.dev/std">Standard Library Docs</a></li>
<li><a href="http://pkg.go.dev">Other Package Docs</a></li>
</ul>

<h1>Community</h1>

<ul>
<li><a href="http://groups.google.com/group/golang-nuts">Go Nuts Mailing List</a></li>
<li><a href="http://stackoverflow.com/questions/tagged/go">Go questions in Stackoverflow</a></li>
<li><a href="http://dave.cheney.net/resources-for-new-go-programmers">Resources for new Go programmers</a></li>
</ul>
</div>

t5_2rc7j

Ask questions and post articles about the Go programming language and related tools, events etc.

<div class="md"><p>Ask questions and post articles about the Go programming language and related tools, events etc.</p>
</div>

Do you like structured logging?