News for hackers. Stuff that matters.
Re:From Java to Go, and Back Again (2016) by jayd16 on Saturday June 23, 2018 @02:59PM (#17382786)
When you only have one implementation, you often have no concept of what a second implementation will look like and you have no idea what concept or task you're delegating to the interface. They just become header files for the single implementation.

Now, you can be good at planning ahead and know what the abstraction should be in many cases. This is still much rarer than all cases. Indiscriminately creating an interface for every class means you're probably not giving the interface much thought.

There are no comments on this comment yet.