Well the point is, "patterns" and other such abstractions should ONLY be used when they're useful and necessary, but some people (not the author!) are adding interfaces everywhere "because they can", even when there's no reason.
It's called overengineering, and it's a main reason why many people came to dislike Java as a programming language (the Java world is pretty fanatic about adding tons of abstraction layers all over the place, whether it's useful or not).
So I say yes, do keep SOLID in mind and make sure you understand its principles, but there are many 'simple' scenarios where you can code it in the simplest way possible and where that would actually be the way to go.
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.
Well the point is, "patterns" and other such abstractions should ONLY be used when they're useful and necessary, but some people (not the author!) are adding interfaces everywhere "because they can", even when there's no reason.
It's called overengineering, and it's a main reason why many people came to dislike Java as a programming language (the Java world is pretty fanatic about adding tons of abstraction layers all over the place, whether it's useful or not).
So I say yes, do keep SOLID in mind and make sure you understand its principles, but there are many 'simple' scenarios where you can code it in the simplest way possible and where that would actually be the way to go.