Looking Backend Dev Learning Resources

[Shubh Karman Singh]

Dear fellow Gophers, 

I have been looking for resources to learn the backend development in Go. I want some good resources which talk about how to write Idiomatic Go Code, the Best Practices to follow, Anti-Patterns to avoid and writing an overall secure server. Any good resources are highly appreciated. 

Thanks and Regards

SK Singh

[Christoph Berger]

If you know the basics of Go already, Effective Go and the Go FAQ are good starting points for learning what idiomatic Go is like and why certain decisions in the language design were made.

[Marcello H]

https://mehdihadeli.github.io/awesome-go-education/

Op woensdag 30 november 2022 om 14:12:46 UTC+1 schreef christoph...@gmail.com:

[Tsvetomir Lazarov]

How relevant is Effective Go actually, given the January 2022 update that this document has not been updated significantly since 2009?

[Dan Kortschak]

On Mon, 2022-12-05 at 09:27 -0800, Tsvetomir Lazarov wrote:
> How relevant is Effective Go actually, given the January 2022 update
> that this document has not been updated significantly since 2009?

Still relevant. This is one of the virtues of having a language that is
not built on the Red Queen model of progress[1].

[1]https://en.wikipedia.org/wiki/Red_Queen%27s_race

[Robert Engels]

Can you elaborate on that reference? At first review, it means you are putting in lots of effort making lots of progress (anti red queen) but that would mean the progress made did not invalidate any of effective Go (which seems not possible given the addition of generics). I’m doubting you implied little effort was put in over 10 years so little progress has been made :)

> On Dec 5, 2022, at 2:19 PM, 'Dan Kortschak' via golang-nuts <golan...@googlegroups.com> wrote:

> --
> You received this message because you are subscribed to the Google Groups "golang-nuts" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/0af2089eb4f34cd5f8e67f1c9b1cad62c1b76e57.camel%40kortschak.io.

[Dan Kortschak]

On Mon, 2022-12-05 at 14:54 -0600, Robert Engels wrote:
> Can you elaborate on that reference? At first review, it means you
> are putting in lots of effort making lots of progress (anti red
> queen) but that would mean the progress made did not invalidate any
> of effective Go (which seems not possible given the addition of
> generics).  I’m doubting you implied little effort was put in over 10
> years so little progress has been made :)

The Red Queen was the definition of churn. She never made any progress.

[Christoph Berger]

> that would mean the progress made did not invalidate any of effective Go (which seems not possible given the addition of generics)

Adding new features makes Effective Go incomplete but not invalid. There is separate documentation available for Generics and other new features. Go documentation can only be invalidated if breaking changes are introduced to the language. But the Go 1 compatibility promise prevents this from happening except for very rare cases like, for example, security fixes that cannot be implemented without breaking existing code.