With the high adoption of the Go language by developers and large companies, this has led companies to search for engineers with experience in Go.
This can create a lot of pressure of what to study to become a better engineer, this is very personal, it requires planning of what and when to study other subjects (even outside the engineering area).
In this blogpost some topics (with repositories and links) that I think are important to know in order to become an engineer person with even better Go knowledge, follow good practices for writing code, concepts of code structure (usually using design pattern), scalable code and clean code.
I can’t list only one link (repository) for this topic, I would recommend you to read for these 3 links and bring to your team’s day to day life what best fits their reality — remember to use as base the official language documentation and add what makes sense from the other links
Go is a new language. Although it borrows ideas from existing languages, it has unusual properties that make effective…
This repository holds the Uber Go Style Guide, which documents patterns and conventions used in Go code at Uber. See…
Google Style Guides
Every major open-source project has its own style guide: a set of conventions (sometimes arbitrary) about how to write…
Go standards and style guidelines | GitLab
This document describes various guidelines and best practices for GitLab projects using the Go language. GitLab is…
Francesc Campoy gave an excellent talk at OSCON 2015 on this subject, where he covered best practices for developing software using the Go language.
Slides Twelve Go Best Practices
Permalink Failed to load latest commit information. The repository is a collection of open-source implementation of a…
This repository contains Go based examples of many popular algorithms and data structures.
Each algorithm and data structure has its own separate README with related explanations and links for further reading.
A reference for the Go community that covers the fundamentals of writing clean code and discusses concrete refactoring examples specific to Go.
This document is a reference for the Go community that aims to help developers write cleaner code. Whether you're…
In his book “Clean Architecture: A Craftsman’s Guide to Software Structure and Design” famous author Robert “Uncle Bob” Martin presents an architecture with some important points like testability and independence of frameworks, databases and interfaces.
This is an example of implementation of Clean Architecture in Go (Golang) projects. Rule of Clean Architecture by Uncle…
Elton Minetto has written two excellent blogposts on the subject:
Clean Architecture, 2 years later
In February 2018 I wrote what would become the most relevant text I have ever published: Clean Architecture using…
I couldn’t leave out the awesome-go project (which I started in 2014 and today many contributors help me maintain)
A curated list of awesome Go frameworks, libraries and software - avelino/awesome-go
A collection of awesome Go libraries and resources. This repository contains a list of variety of frameworks, template engines, articles and post, documentations, reactive and functional programming and much more which will increase your resourcefulness and might also help you to choose the tech stack for your next projects.
This is a complicated subject, there is no standard that will work perfectly for what you are developing, I recommend understanding the concept of project architecture (not only Go) and together with your team understand what works for you, even though there are thousands of books to give you knowledge about the subject I recommend putting your hands in the code and allow you to make mistakes, it is the best way to evolve.
Read this content before any other
How to Write Go Code
This document demonstrates the development of a simple Go package inside a module and introduces the go tool, the…
Now that you have read the previous link I will recommend a controversial repository by its name, it is not “Golang standards project layout”, but there is a project structure that can help in the development of a new project — understand what makes sense for you (and your team), what doesn’t, just ignore it.
Translations: This is a basic layout for Go application projects. It's not an official standard defined by the core Go…
Vote Of Thanks
Thank you so much for reading this post and I hope you find these repositories as useful as I do and will help you to become better go developer. Feel Free to give any suggestions and if you like my work you can follow me on Twitter
Originally published at https://avelino.run on July 11, 2021.