Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
!rant
Interview prep question. My understanding now is, at least in theory is: always use SOLID. I've never really understood it explicitly though I think I follow it a lot in practice, just naturally...
But when I usually program I'm kinda of in between... I don't automatically default to it.
Particularly, I don't always create interfaces, at least not in the first pass unless I know or expect many different implementations of a certain component... Or just because I need some class that does X but haven't quite thought of the implementation.
But I have never created an interface with like only 1 property or method... Kinda feel that's overkill...
I tend to follow DRY more I guess...
What's everyone thoughts on this stuff?
undefined