Don’t ever mention OOP during an interview. I swear it’s such an odd topic of contention, you will flat out get passed up for mentioning it in any sort of positive light.
Yet if you employ the paradigm cleanly and in the right context, devs get impressed and start borrowing designs.
OOP debates usually turn into inheritance vs composition which is weird because every modern used language has objects and most OOP languages lean towards composition these days.
The core OOP concepts are universal and important.
Greate writeup.
Don’t ever mention OOP during an interview. I swear it’s such an odd topic of contention, you will flat out get passed up for mentioning it in any sort of positive light.
Yet if you employ the paradigm cleanly and in the right context, devs get impressed and start borrowing designs.
So weird.
You can also just refer to the principles; at this point OOP is more of a buzzword with too much association with enterprise Java
OOP debates usually turn into inheritance vs composition which is weird because every modern used language has objects and most OOP languages lean towards composition these days.
The core OOP concepts are universal and important.