A useful conversation. I majored in CS 24 years ago (am I old now?) and have had my fingers and toes just about everywhere in the last few decades. I think yo

A useful conversation. I majored in CS 24 years ago (am I old now?) and have had my fingers and toes just about everywhere in the last few decades. I think your definition is pretty good but I think the primary question/problem is that too many people who don't really understand what it means just throw it around — especially in management/hiring/hr/etc. At the end of the day, if you wanted to be nit-picky the response would be "what stack?" because no one is the master of all stacks and all things. I have worked with some amazingly talented people in my career and everyone has gaps, unless you're constantly learning and never building. Maybe the real question/concern is that they're going to expect you to do N jobs and only pay for 1. What you should really look for when you hire people isn't what they claim to know and ace on a "is X a native type in Y?" they question but instead how they think and how they can learn. Developers who are curious and want to learn are far better imo than ones that claim they know everything.