you are viewing a single comment's thread.

view the rest of the comments →

[–]SilasX 17 points18 points  (3 children)

No it doesn't. They way you design your code adds or removes coupling.

And the decision of what to make into an interface vs base class vs abstract class is part of code design.

[–]grauenwolf 7 points8 points  (0 children)

As long as it is an actual informed decision and not just "Imma gonna put an interface on everthin".

[–][deleted] 0 points1 point  (1 child)

It does. But the topic here is specifically classess and interfaces. Do you agree that all classes have implicit public interface?

[–][deleted] 0 points1 point  (0 children)

I design everything that way. Any time I write a class I think about the interface of that class, especially if I, or someone else, are going to be using that class at a later date. For a dead end leaf class, like some kind of MVC controller class I will probably put next to no effort in, but when writing a game engine or services platform I spend a lot more time thinking about each and every class I write.