Good practices

Formatting

Packages should have a top block comment for documentation - multi file packages should only have one comment.
Comments are plain text, no annotations for formatting is needed.
Comments preceding top-level declarations are used for documentation. Every exported name should have a doc comment.
```
// Foo is an example of how doc comments should be.
func Foo() {
	return "foo"
}
```
Related constants or variables may have only one comment to introduce them.
```
// Dimentions of something.
var(
	length uint32
	width uint32
)
```

Names have a semantic effect in Go. So naming is very important.

Package names should refer to it's content. They should be short, concise and evocative. Package names MUST:
- Have one word.
- Be lower case.
- NOT have mixedCase or under_scores.

Getters and setters may be used when necessary.
Getters should not take the prefix get . If there's a field name it's getter must be called Name .
Setters should take the prefix set. If there's a field name it's setter must be called SetName .

One-method interfaces should be named with the method's name followed by the suffix er . E.g. Reader , Writer .
Well-known method's names such as Read , Write , Flush, Close, should only be used if they have the same signature and meaning. E.g. a string converter should be called String not ToString.

Array pointers like array *[10]float64 are not idiomatic and should be avoided. Slices should be used instead.