Hello, Praveen
Thanks for the response!
Actually this article is about our unique experience in solving codebase maintainability issue as an organization by choosing Go rather than the feature of Go as programming language itself. This was why we are focusing more on the impact in our organization. 😃
Also the things that you mentioned are actually not issues for our organization. Here are the details:
- Error handling, it was good initially, but after writing err != nil for everything, I felt it's little annoying.