Mastering Go: Leverage Go's expertise for advanced utilities, empowering you to develop professional software 4th Edition

Great Book, Dives right in and really digs into details. Ive been using go for about 4 months before getting this book and 4 chapters in I can already tell I am better.

Recently I'm having a hard time finding actually usefull programming books, it is too easy finding the information you need on internet. The reason why I buy a book instead of reading the documentation is because I need an explanation on topics that are hard to understand and when to use tose concepts. Like goroutines, generics and thread sync. This book does a really good job making you understand hard concepts.I have not read the first chapters that explain the basics of go, but I supose if you never programmed before they have to be good.

Note: I was given a free review copy of the book. Additionally, I was unable to spend a vast amount of time reading word by word, line by line, so I read through some of the things which more interest me at my level. I would say that I am an intermediate Go programmer and leverage it for primarily backend services.TLDR:Pros: Book is a good primer for those just beginning to learn go, or into an intermediate level. The book is large with a lot of points being hit, and it being updated to new versions of go is great. It leverages a lot of Linux ideas which is great of where go tends to shine: backend development for Linux OS.Cons: Book organization is a bit wanting with where topics have been placed (see logging below as an example). Much of the material is just at touch level, and could have had better examples, or a few longer running examples.Overall, I'll give it a 4 out of 5 stars with the idea this book is meant for people just beginning their career. I do not think this was do much for people firmly within an intermediate skill level with a few larger apps written already by them.Reviews on specific topics:Exercises: One thing that I love about books are great exercises, especially if they relate to tools that I leverage on a daily basis, mainly linux operating systems and databases, and have an actual use case for me. I believe that this book's exercises pretty happily satisfies my desires. Many of the questions deal with command lines, linux systems, files, etc., all things I work on. Many build off of what was started within the chapter challenging you to implement a new feature, fix a bug, etc. If there was an issue with them, I would say that there does not appear to be hints/outputs/answers for you to see how you did. Maybe the author, on his github site for the book could add that.Logging: Logging is a big part of my job and I believe this book only touches on it's importance. It accurately reflects many of the ideals that exist out there now with how to long, giving examples as well. The book is newer and eventually mentions the new structured log (slog) package, but that was buried pretty deep in the How To Tell Linux What to Do section. It lacks depth in instantiating and how to pass your logger around your program, likely due to it's so early of an introduction on the topic.structs and interfaces: The book goes into some detail on structures, methods, and interfaces. The discussion around them is alright, but the examples is really lacking to show the power of what can be done with them.Context: Has a pretty good amount of information on leveraging contest. The examples are simple, so more depth would have been appreciated, but overall a pretty good coverage.Testing: A good amount of testing is there and enough to get new programmers' feet wet. One can not stress enough how important testing is. This book will help you get started but you'll likely be looking for another source on the matter.pointers: Book discusses the simple use case for them, and garbage collection around them, but outside of an example of putting a pointer in a simple map, there isn't much here. Pointers was one of the harder things for me to learn coming from Python, and is crucial for new programmers to understand. I would have liked to see more real life examples with leveraging pointers.Global variables: Just don't do them, unless it is a global static. Section does not touch on this and appears to have global variables leveraged within the code.

I have to say that usually when I get a programming book I have to modify the code in it to make it run. That’s great for learning if you’re someone like me who will tinker to make it work and learn as you go, but for everyone else it stops forward progress and they stop trying. This book is for people like me and everyone else. The code is clean, precise, and works the first time through, no tinkering required! The explanations are very good, too! This is definitely a buy if you want to learn Go or have a reference if you already know the language!

Mastering Go is a one stop shop for being able to learn Go from beginner concepts to advanced and everything in between. If you are looking for an easy to follow and really well written book that will cover all that you need to understand and write Go then look no further. This book is a great resource for Go developers. Whether you are an experienced Go developer or a beginner this book has something in it for you.

I recently had to use Golang and I was looking to refresh my mind since it's been a few years. I was able to read through this book and it helped me to get a good refreshment of the language and ecosystem since things have changed quite a bit in Golang since I learned it a long time ago.

I recently finished reading the blue book (“The Go Programming Language”) and picked up this one to learn more about Go’s more recent language features and also get another author's take on things.From the sections I have read I’ve found that the content is good. The examples provided are concise and to the point, while the explanations provide an expected level of detail.After reading more I hope to return to this comment to provide a more complete review.

The Great:1. Nice usable examples of each concept.2. Information is crisp and verbosity is efficient.3. Touched all aspects of coding with go.4. Touched info on Gorilla mux and gin which are most ppopular microservices frameworks in go.5. Really good content overall.The things which could’ve been added:1. Could have included better nested examples for encoding/json.2. Could have eased into go build later after go run in intro.3. Could’ve added more info and understanding examples on usage Prometheus and Grafana.4. Could have explained nested routes now available in go 1.22.5.Could’ve added working with Docker file should be a separate chapter and in further detail. Even better if K8s could be introduced with that or AWS usage of docker images.Slight misses:1. Thread safety of map and slices and the lazyquotes of csv (common problems).2. Misses testing.M implementations/usage in testing.3. Heading should be value and pointer receiver not value and point receiver (its a typo).4. Shallow and Deep copy could’ve been explained more in detail.5. Some very minor technical mistakes: ex: fork (makes processes not threads). error is an interface type (reference type) not a data type.Note: This is just my review of the book looking at the review copy.