Building an interface (even if there's only one implementation) is unquestionably right

This site does not allow itself to be embedded. You can still read it on the original site — the toolbar below keeps your place in the directory.

tl;dr - Large components of systems you build deserve an interface, even if there is only ever one implementation. If you want your code to be good, put a bird interface on it! I’ve gone back and forth, but for the last maybe 5 years my opinion has hardened. My stance is now that it is unquestionably right to always build an interface for large components of a given system, even if you only…

Read on vadosware.io ↗