title: golang variable naming convention across packages
body: <p>Recently I started studying go-ethereum and this was my first time using golang. C++ is my main language and I'm a bit puzzled due to variable names in go-ethereum project.</p>
  
  <p>core/state/managed_state.go:25:type account struct {</p>
  
  <p>core/state/state_object.go:98:type Account struct {</p>
  
  <p>There are both "account" and "Account" types in state package, which seems weird.</p>
  
  <p>I've checked <a href="https://stackoverflow.com/questions/40881994/naming-convention-for-similar-golang-variables">Naming convention for similar Golang variables</a>, and it still looks terrible.</p>
  
  <p>And what I've found is that they use a lot of "Node" struct in different packages. Definitely they do have different purposes and structures. </p>
  
  <p>Are these kinds of naming is convention and popular in golang? 
  If you have any good references for naming convention in golang (e.g. open source projects or books), could you please name some of them? It would be really appreciated.</p>