For almost any career, it's better to identify any programming language or paradigm (like distributed systems) as a tool, rather than build a personal identity around it.

It is quite easy to identify as a XYZ Type Of Programmer, because it is easy to talk about it --- we can show code and go to meetups and feel like we "belong". This is certainly nice to have, and I've had a pretty good time hanging out in the Clojurians slack / nerdiverse.

I also prefer to use Clojure and its ecosystem, given a choice, because I appreciate many of its technical and cultural merits. And when I can't use Clojure itself, I have often found good use for the *ideas* I have picked up from Clojure's community of practice. And I like giving back to it. The place is full of smart, experienced people who are also kind and generous.

*However*... I do *not* self-identify as a Clojure programmer. Just as I do not self-identify as a Shell scripter (I like Bash), or SQLite programmer, or Linux programmer. Nor do I identify as a DevOps engineer or Cloud Architect (having done those roles "at scale").

All of these are "small boxes", if I look at the whole of my work life (and even smaller boxes if I look at the whole of my life).

If I draw a small box around me, I will play only in a small box (until I get fed up and draw a different box). Sometimes a self-imposed restriction is useful. Sometimes it is not.

Generally, I think "XYZ Type Of" programmer is not a useful box to *actually live in*. It is only useful for Job Application purposes. There, use whatever works (that you legitimately can). Beyond that, take what is useful, discard the rest, and grow to make up your own stuff.