By team I mean team culture and general go culture. And I don't mean attitudes or treatment. I mean design philosophy. Just to be clear. No links just look at some go libraries. Many libraries feel like it's designed for java.
Your opinion here is just bizarre because typical Go code is as far away from typical (bad) Java code as you can get.
Your typical Go library doesn't have FactoryFactory classes, doesn't overuse interfaces, doesn't have dependency injection, doesn't have callstacks 20 frames deep etc.
So yeah, I would like to know which Go libraries specifically you're referring to because I just don't see that in the popular Go packages.
Some people need to justify their salaries with the complexity for nothing.
To understand idiomatic go, it is better to look at its own standard library source codes.