Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
Clueless1353283d@torbuntu It's not an interview, but a common OOP questions that I got recommended from my relatives. I told them I'm not an OOP guy but applying the concepts of Design patterns to both OOP and FP world.
nanhb1574283dactually thats something that you prove when you design a solution..
matste698275dOnce someone asked me what SOLID stands for. I screwed up the D - it’s apparently not Don’t Repeat Yourself. The hiring architect wasn’t happy.
To this day I don’t understand this fascination of SOLID during recruitement. You show that your code is clean by writing it, not by recitation of formulas. Workplace is not Sunday school ffs.
S is impossible to define and therefore useless.
O is obsolete.
L describes rules for code that should not be written in the first place.
I is fundamentalism
D (dependency inversion principle) is OK, but totally obvious.
Lucky-Loek298246dThe four pillars of OOP are:
1. Sun's marketing budget
2. IBM's marketing budget
3. Microsoft's marketing budget
You can do everything that any OOP language does in C, except for interfaces. Encapsulation was even better with header files. None of that public/private/protected bullshit.