guide

Additionally... - https://go101.org/optimizations/101.html - https://github.com/uber-go/guide I wish this content existed as a model context protocol (MCP) tool to connect to my IDE along w/ local LLM. After 6 months or switching between different language projects, it's challenging to remember all the important things.

I think a useful iteration of that pattern is one called Functional Options: * https://dave.cheney.net/2014/10/17/functional-options-for-fr... * https://github.com/uber-go/guide/blob/master/style.md#functi...

Yes, definitely dozens of pretty good online resources. Here are 3: - Tour of Go: https://tour.golang.org/ - Practical Go: Real world advice for writing maintainable Go programs, by Dave Cheney: https://dave.cheney.net/practical-go/presentations/gophercon... - Uber Go Style Guide: https://github.com/uber-go/guide/blob/master/style.md

Copy Slices and Maps at Boundaries: https://github.com/uber-go/guide/blob/master/style.md#copy-s... The suggested good clone is not very efficient: https://github.com/go101/go101/wiki/How-to-efficiently-clone... In fact, I prefer the suggested bad one instead. We should let the caller to determine whether or not a clone is needed. -------------------------- Start Enums at One: https://github.com/uber-go/guide/blob/master/style.md#start-... Any reason here? (Edit: I just missed the reason. However, I think there should be a default value for most enums and most of the default values should zero.) -------------------------- Local Variable Declarations: https://github.com/uber-go/guide/blob/master/style.md#local-... Personally, I prefer "var x = ..." and think short variables should be used as limited as possible. I remember that Go team has

I find it amusing that the advice in the style guide gives a good example contradicting another good example, and contains a subtle bug. In the "Reduce Scope of Variables", second good example leaks an open file when WriteString fails, because it doesn't follow the own advice of "Defer to Clean Up" if you are curious. (Handling that properly with a defer is a bit more tricky - something like https://play.golang.org/p/l1PeWM3Tisg). Update: style guide was fixed after this report :) It was this if you wonder: https://github.com/uber-go/guide/blob/a53ee0bef8c0b11b52340d...

I really like the horizontal 'Good/Bad' code comparisons in this guide. I didn't realize how horizontal vs. vertical code comparison affects readability; IMO horizontal is MUCH more readable. Example: https://github.com/uber-go/guide/blob/master/style.md#defer-...