4 ms·
Perhaps there’s a difference between knowing and having internalized these concepts, versus having heard of them via a particular acronym, and being expected to
by AgentOrange1234 3y ago
Perhaps there’s a difference between knowing and having internalized these concepts, versus having heard of them via a particular acronym, and being expected to remember that acronym and these specific names.
“Liskov substitution principle” for instance is something I had to look up. I can read it and say, “oh, duh, yes that’s a key part of what interfaces are even for.” I’ve built with it for decades now.
The term SOLID was apparently introduced in 2004. It would be a shame to reject good programmers who can opine intelligently on these principles, but who have not internalized this particular jargon.
- MyFedora 3y agoYes, there is quite a difference in my opinion. What does SQL stand for? No clue, but I can write you an SQL query. Same thing with HTML, CSS, PHP, etc.
- jval43 3y agoThat's funny. I wrote SQL daily for 10 years, read the ISO standards when working on SQL transpilers, persistence frameworks for multiple databases, etc. Even wrote a new storage engine for MySQL once. But I just had to look up what the acronym stands for! Apparently it's "structured".
- mytailorisrich 3y agoIsn't that the point? Even if the candidate doesn't know the acronym you can probe if they know and understand, and be critical of, what the principles are.
- deleted 3y ago[deleted]