Interfaces and abstract classes are code bloat if you ask me, and they are a waste of time why should I define a method signature then later implement it. Seems like a extra step for no reason to me.
I had a similar feeling in the past especially working with code where someone made an interface for every single object. However, now I see the use cases for library components and making code more flexible for use. Code can sometimes be too strict in what it allows and an interface allows a more generic option to be used that still matches the contract.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Interfaces and abstract classes are code bloat if you ask me, and they are a waste of time why should I define a method signature then later implement it. Seems like a extra step for no reason to me.
I had a similar feeling in the past especially working with code where someone made an interface for every single object. However, now I see the use cases for library components and making code more flexible for use. Code can sometimes be too strict in what it allows and an interface allows a more generic option to be used that still matches the contract.