> If you take a look at any codebase, build by experienced senior developer or junior dev straight out of college/high school the code is almost always the same

> If you take a look at any codebase, build by experienced senior developer or junior dev straight out of college/high school the code is almost always the same I think that's kind of the point though. Go gives you one way to do things, and makes it really easy to read no matter what your level. It makes things very boring, which imo is a good thing in lots of cases. Its also terrible for some use cases because it is quite verbose (as you mentioned, err != nil can get tiresome if errors don't matter much), so you gotta find a good balance.