[superswordfish]

Yes. I've worked with a handful of career Python developers, and they're even worse than career Java developers (at least the Java stack tends to be deep and sophisticated, demanding some expertise). They are practically useless when you depart the world of WSGI and new-style vs. old-style classes. At this point, people like that are an automatic thumbs-down during an interview for me.

Why is that? Think about it: How many jobs have you ever worked where you only had to know one language, or one stack? What sort of person would desire to work on the same stack, job after job? Who wouldn't have the curiosity or professionalism to branch into other areas on the job? I've never in my career encountered a full Python stack. There's at minimum some combination of C, C++, SQL, or JavaScript.

I believe there are two kinds of developers: Those who try to fit the world of software into their own mental model, and those who try to learn the model of the world of software. The former cling to the first technologies with which they achieved proficiency. The latter feel the urge to expand their horizons, so that they can better understand their early learnings in the larger context of computing, a pursuit that hones all software development skills.

Who do you want to work with?

[izolate]

When I was starting out, I'll admit I looked up to career Pythonistas in awe. One day I thought I'd get there, but never did. I have a favourite language that I know best, but I'm totally agnostic.

I look forward to my development career being summarised as a series of different favourite languages/ecosystems as I explore and progress.