The fight against interfacitis must go on!
-
Glad Miguel Icaza share my sentiment! :D [Miguel de Icaza on Twitter: "This goes to the core of why I dislike abstractions and interfacitis. People are designing software as if@it should eventually allow a plugin to send e-mail, emulate Emacs, plug a GPU pipeline, use the blockchain to sto](https://twitter.com/migueldeicaza/status/1076891079482454016)
A new .NET Serializer All in one Menu-Ribbon Bar Taking over the world since 1371!
-
Glad Miguel Icaza share my sentiment! :D [Miguel de Icaza on Twitter: "This goes to the core of why I dislike abstractions and interfacitis. People are designing software as if@it should eventually allow a plugin to send e-mail, emulate Emacs, plug a GPU pipeline, use the blockchain to sto](https://twitter.com/migueldeicaza/status/1076891079482454016)
A new .NET Serializer All in one Menu-Ribbon Bar Taking over the world since 1371!
Interfacitis :laugh: that's what I'm going to tell my colleague who is so fond of creating interfaces for even the most simple of applications !
-
Interfacitis :laugh: that's what I'm going to tell my colleague who is so fond of creating interfaces for even the most simple of applications !
Love them while building, hate them while debugging. Guess how often I use them?
Wrong is evil and must be defeated. - Jeff Ello
-
Glad Miguel Icaza share my sentiment! :D [Miguel de Icaza on Twitter: "This goes to the core of why I dislike abstractions and interfacitis. People are designing software as if@it should eventually allow a plugin to send e-mail, emulate Emacs, plug a GPU pipeline, use the blockchain to sto](https://twitter.com/migueldeicaza/status/1076891079482454016)
A new .NET Serializer All in one Menu-Ribbon Bar Taking over the world since 1371!
-
I must be doing something wrong. I don't use interfaces all that often.
Everyone is born right handed. Only the strongest overcome it. Fight for left-handed rights and hand equality.
From what I have seen, and I might be wrong here, that's a disease that seems to strike web developers the hardest.
A new .NET Serializer All in one Menu-Ribbon Bar Taking over the world since 1371!
-
Love them while building, hate them while debugging. Guess how often I use them?
Wrong is evil and must be defeated. - Jeff Ello
As you do lots of debugging, the following quote is appropriate:
Quote:
… Es regiert der Herr des Hasses Hässlich ich bin so hässlich so grässlich hässlich ich bin der Hass! Hassen ganz hässlich hassen ich kann's nicht lassen ich bin der Hass! Attention Attention unknown flying object approaching the planet!
:-\
-
From what I have seen, and I might be wrong here, that's a disease that seems to strike web developers the hardest.
A new .NET Serializer All in one Menu-Ribbon Bar Taking over the world since 1371!
-
Glad Miguel Icaza share my sentiment! :D [Miguel de Icaza on Twitter: "This goes to the core of why I dislike abstractions and interfacitis. People are designing software as if@it should eventually allow a plugin to send e-mail, emulate Emacs, plug a GPU pipeline, use the blockchain to sto](https://twitter.com/migueldeicaza/status/1076891079482454016)
A new .NET Serializer All in one Menu-Ribbon Bar Taking over the world since 1371!
I think like many things it's a case of degree. Interfaces by themselves are not evil and used properly when needed they make development much easier - because you can rely on dependency injection rather than tightly coupled code(I probably don't know what I am taking about here but I thought I would use some jargon...). There are case where interfaces have made things a lot easier for me - recently I was hitting an issue with an email class I was using, so instead of rewriting a whole bunch of code I created an interface and passed in the new class by interface. I then discovered that there was a way around the issue I had and did not need to use the new library, so all I needed to do was to reference the old class when passing the mail class by interface - it took less than 5 seconds to reference the old class again. In my work life I work on a huge application with all sorts of interfaces and it does make debugging a lengthy process - so like anything else when overused they can cause problems.
“That which can be asserted without evidence, can be dismissed without evidence.”
― Christopher Hitchens
-
Glad Miguel Icaza share my sentiment! :D [Miguel de Icaza on Twitter: "This goes to the core of why I dislike abstractions and interfacitis. People are designing software as if@it should eventually allow a plugin to send e-mail, emulate Emacs, plug a GPU pipeline, use the blockchain to sto](https://twitter.com/migueldeicaza/status/1076891079482454016)
A new .NET Serializer All in one Menu-Ribbon Bar Taking over the world since 1371!
Interfaces are not inherently bad, nor are they the problem. It's the (non)discoverability of the concrete implementation which makes using an interface problematic. Much of the time one is looking at an interface, it's because some [perceived] bug is brought up; thus, you're really trying to find the implementation. The problem comes about when that implementation is abstracted away in a manner that the researcher "just has to know about"--some configuration file on app startup or whatever--as opposed to a more inline factory-type "GetImplementationForX(params)" which the developer can trace and discover that, in the error condition, it's implementation #n they need to research. Fortunately, a lot of that discovering is made easier with modern tools, where we can right-click and see the implementations of IWhatever, so it's not as bad as it once was. I definitely agree with the aspects of over-engineering (i.e., trying to cram extra functionality where it doesn't belong) and trying to solve problems which don't exist being an issue though.
-
Glad Miguel Icaza share my sentiment! :D [Miguel de Icaza on Twitter: "This goes to the core of why I dislike abstractions and interfacitis. People are designing software as if@it should eventually allow a plugin to send e-mail, emulate Emacs, plug a GPU pipeline, use the blockchain to sto](https://twitter.com/migueldeicaza/status/1076891079482454016)
A new .NET Serializer All in one Menu-Ribbon Bar Taking over the world since 1371!
This is what happens when you abandon software engineering principals and use junk-paradigms like Agile, MVC, and the like...
Steve Naidamast Sr. Software Engineer Black Falcon Software, Inc. blackfalconsoftware@outlook.com
-
I think like many things it's a case of degree. Interfaces by themselves are not evil and used properly when needed they make development much easier - because you can rely on dependency injection rather than tightly coupled code(I probably don't know what I am taking about here but I thought I would use some jargon...). There are case where interfaces have made things a lot easier for me - recently I was hitting an issue with an email class I was using, so instead of rewriting a whole bunch of code I created an interface and passed in the new class by interface. I then discovered that there was a way around the issue I had and did not need to use the new library, so all I needed to do was to reference the old class when passing the mail class by interface - it took less than 5 seconds to reference the old class again. In my work life I work on a huge application with all sorts of interfaces and it does make debugging a lengthy process - so like anything else when overused they can cause problems.
“That which can be asserted without evidence, can be dismissed without evidence.”
― Christopher Hitchens
Man, you don't understand interfacitis. Interface are good they can solve problem! :) Interfacitis is when interface becomes the goal without any particular end and introduce problem instead of solving them... Interfacitis is like when people tells you "always create an interface before creating the class or when one create an interface with 42 method and growing, constantly... It's like.. water is good. Too much water, you drown!
A new .NET Serializer All in one Menu-Ribbon Bar Taking over the world since 1371!