This is true for life in general, but I'm not sure it works for technical interviews.
I've seen many candidates derail themselves by trying to tell interesting stories without realizing that the interviewer doesn't care. Many companies treat technical interviews as a test and have strict rubrics that are specific to the question.
If I ask a candidate:
"Okay, but how would you replace that XMLHttpRequest with fetch?"
all I want is a straightforward answer that shows you know the answer to the question, or an explanation of why you don't, ex:
"Oh, I would Google that. I exclusively used Axios in my prior job but I could learn fetch in an hour or two"
I know you want to feel heard and I will listen if you want to tell me how you fought your boss and won in a quest to replace all of your homegrown internal tooling with jQuery, but pay attention to your interviewer's body language and responses.
In general, my advice for an interview is never talk more than 1-2 minutes without getting active encouragement from your interviewer to continue on the current thread of conversation.
