Regardless of everything else I'm afraid that job-market-wise OOP is dominating which makes it difficult (at least for me) to do serious knowledge investment in FP.
OOP related I've seen it used nicely -usually when kept as simple as possible and mostly as a message passing mechanism. But more often than not it ends up as a big ball of mud or an overengineered mess of design patterns and opinionated (to the point of cargo-culting) principles (SOLID etc). Specially from younger devs.
Excuse my ignorance but I'm wondering how difficult/feasible would it be to have all CO2 captured from burning coal etc and thus making them zero emission.
Senior dev (>10 yoe). Not the type that looks down on people and not a fanboy or an evangelist of any sort. But I regard developer experience highly. I.e. I hate to have to spend days to fix a dev sandbox before I even start doing my job.
Yeah, that -together with going through all the interviews/take homes/etc again- is the biggest inhibitor. Dunno, maybe it's time to start considering a total career change. I'm fed up with the actual reality of doing SW engineering for a living.
Manager agrees on most of my points but, for various reasons, he cannot/won't change anything. All he can do is chase up people to set up a knowledge transfer meeting (when excessive meetings are just a sign of the dysfunctions of other levels).