1. Capitalization. Author cited they didn't want to change how they named things and it conflicted with Go export rules. Okay then. > 4. A very good one: "Here

1. Capitalization. Author cited they didn't want to change how they named things and it conflicted with Go export rules. Okay then. > 4. A very good one: "Here’s far too much magical behavior. For example, if I name my source file i_love_linux.go, it won’t get compiled on my Mac. If I accidentally name a function init() it’ll get run automatically. (...) It’s fine for small projects but bites you on large ones, and Go was meant to address the problem of “programming in the large”." 4. is great for large projects. Once you learn the convention, it is super easy to see which files are for which platforms. It makes it to navigate large trees. 6. Look at how protobufs do it. Easy to work around. 11. Understand how Go works, run go vet.