# 4 "This is all part of the “convention over configuration” movement. It’s fine for small projects but bites you on large ones, and Go was meant to address the

# 4 "This is all part of the “convention over configuration” movement. 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”." Isn't that the opposite? conventions (even ugly ones, or annoying ones) help with consistency across many developers or large projects.