Interface Design Nets Policy: Is It Really As Good (or Bad) As They Say? - OpenSIPS Trunking Solutions

Do define an interface if you need some common api to be supported by a set of types that includes value types. Read also: What Top Scientists Say About The EMF-CNF Connection And Your Risk

Consider defining an interface if you need to support its functionality on types that already inherit from some other type.

Avoid using marker interfaces (interfaces with no members). Read also: Craigslist Lincoln Listing: The Clues You've Been Missing

If your design includes empty interfaces that types are expected to implement, you are probably using an interface as a marker, or a way of identifying a group of types. Read also: The Slayeas Leak: A Whistleblower's Explosive Claims You Need To Hear

If this identification will occur at runtime, the correct way to accomplish this is to use a custom attribute.

Website accessibility ensures that people with disabilities or limitations can easily navigate and access the content on your site.

I agree, interfaces don't need to look good, but it is important to focus on good design, as that improves the user's impression and engagement with the product.

Yes, that should come secondary to function, however.