Stop Writing Go Like It's Java: 5 Patterns You Need to Unlearn

Interfaces everywhere, error handling as an afterthought, OOP hierarchies — the habits that make your Go code worse, not better.