Go Design Patterns

Ogni pattern e' accompagnato da una serie di test. Non e' un libro sul TDD, quindi non si trovano tutti gli step della metodologia. Anzi, ... ci si concentra sopratutto sul design pattern. Mi sembra un ottimo testo. Sono solo ai primi capitoli ma mi sento gia' in dovere di consigliarlo. Mi hanno parlato di questo libro sullo slack ufficiale di go, nel canale #italy. Credo sia poco pubblicizzato, e che valga ogni singolo centesimo speso per acquistarlo.

I just started reading the book and the largest part of examples are wrong... variables declared and not used (the intent was to call other variables), dublicate arguments call, function values return not specified.... Did they just try the code they wrote? I have doubts about it. One start because you cannot deliver a product like this. The star is for the author and for Packt too

This book falls into the category of other poorly written OOP design programming books. It is riddled with errors and lacks a lot of reasoning and examples for each pattern. The examples used in the book are also the tragic abstract examples that have zero real world use. Instead of describing how a a design pattern could be used, it uses examples with objects Cars, or Tshirts which have fields like NumWheels, or Size. All of it is useless outside of the poor example in the bookOn the subject of patterns. The patterns presented are just the Gang of Four OOP patterns which are shoehorned into the Go language. They are not go idiomatic and a lot of the examples should not be used to write idiomatic code. If you are just learning Go this book does a poor job of describing the language and also teaches you how to be a OOP/Java programmer in a different language

This book is horrible. It was very poorly thought out. I couldn't get through two chapters before quitting. The publisher should be embarrassed at producing such junk.

The book is a good attempt at explaining the Gang of Four patterns using GO. Its main problem is the code examples; which are riddled with inconsistencies and errors. I would have given it a higher rating if this was not the case. The code examples that are supplied by Packt (the publisher) for download are correct though. It seems to me that the book was a rush job and it might have done with the editor giving it "the once over" before publishing. Great potential, hopefully fixed by 2nd edition.