Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
Clueless96519d@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.
nanhb160019dactually thats something that you prove when you design a solution..
matste55410dOnce 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.