There is maybe 1 in 10 or 50 Young devs that had luck to work in something like good dev agency and build serveral projects to gain needed experience.
For me age doesn't matter that much because:
* You could be 50 and worked on 2-3 projects entire life * You could be 30 and worked on 25 projects or more.
To be fair, I've been programming enterprise systems for 6 years now and haven't been interviewing in at least 18 months. This question threw me off. Once I googled it and read a whole two paragraphs it jarred my memory and I can speak to it. I can speak to what they do and when I would use one or the other. I can also reference real-world situations where I implemented a queue or a stack.
But lately I've been knee deep in data analytics for the last 18 months and simply haven't touched those "queue / stack" tools in a while. So I needed a "quick lookup" to refresh my memory.
Now if I was actively interviewing, this might be something I would review, as it's a fairly common interview question.
> There is maybe 1 in 10 or 50 Young devs that had luck to work in something like good dev agency and build serveral projects to gain needed experience
This seems like it's implying that knowing the difference between a Queue and a Stack is a good indicator of experience.
How do you figure that as a good signal?
Queue vs stack is an extremely basic concept. They're not even unique terms to CS. You can almost guess what they are just by their names.