Hmm, I have known the formal definitions and not too long ago, I think I know all the elements and I certainly know what to actually do, however I couldn't define the forms without looking them up. Not worth actually doing until an interview as I'd forget it anyway IMO!
Similar here. There is a lot of mundane stuff out there you just can't speak to in terms of correct and technical definitions. Doesn't mean you can't do it or understand it.
For example, I played guitar for 10 years, still can't read sheet music. I still don't hold the neck right compared to what a guitar teacher showed me. I still can't name all the notes, but I still play very complex music.
But there are certain things too, like point-in-time recovery. If you're working with a mission critical system, the time your wasting to look it up, some doctor may not be able to access critical information to save a patience life versus the senior DBA who actually knows his stuff is midway through the recovery while you are still on Google reading some SQLServerCentral.com post from 2014 that Jeff Moden made. :crazy:
Actually I've only read up to Jeff's 2011 but I get your point.
I'd explain it to the interviewer like we were both 5:
When you are dating someone in hot demand, you have to be around her all the time, like putting you name all over her to keep away jerks in the bar.
Then you get married - the relationship established. You no longer need to be around 24x7. In fact you may crave a bit of alone time. That's what we call Normalization. So tell me again please the part about 4-week paid vacation in the compensation package...
If you were to malign red-blooded men who are simply acting upon our most natural of instincts as 'jerks' at interview, well I hope your tech skills are top-notch, if not you can expect a 'No thanks' email via the recruiter from me.