Clean Code: Interfaces in Go - Why Small Is Beautiful
SMRTR summary
Go interfaces work best when kept small, with most standard library interfaces containing just one method like Reader or Writer. Teams often create bloated 10+ method interfaces that become impossible to test and maintain, but Go's approach favors single-method interfaces that can be composed together, following the principle of accepting interfaces as parameters while returning concrete types for maximum flexibility and testability.
SMRTR provides this summary for quick context. The original article belongs to Hacker Noon.
Read the original article