I consider myself a passionate developer, and while strive to put myself into scenarios and projects where that is a plus, it's generally not the easiest route.

I consider myself a passionate developer, and while strive to put myself into scenarios and projects where that is a plus, it's generally not the easiest route. People who care about what they're doing technically become bored or aggravated easily in their daily work. Being opinionated about things that are considered taboo is not always a good thing either, especially if that goes against common tropes or when you're on a buzzword-driven project. It's also easy to aggravate other passionate developers if there are different opinions. Passion-induced skepticism about a solution or tech stack can sometimes even be construed as incompetence. If your passion is programming in general, chances are you have a broad experience background, which is not always perceived in a positive light by management. I recently had a meeting with a potential client who told me they would not hire me because they found it strange and implausible that someone would be able and willing to do both script language programming and also develop native modules in C. I would say, all things being equal, non-passionate developers are very feasible career-wise and absolutely essential for many projects, because chances are they're going to be doing the brunt of the work. Especially in a team, these players are important for follow through. I like to think of teams as RPG adventuring parties: you need people from all character classes to make it work. While all-mage or all-beserker parties can sometimes pull through, a balanced and diverse approach is a better generalized strategy. You want tanks and support characters.