I use functional programming as I've done my fair share of fixing stupid bugs at silly times in the morning and the resulting firefighting. In my experience, I

I use functional programming as I've done my fair share of fixing stupid bugs at silly times in the morning and the resulting firefighting. In my experience, I/teams I've worked on produce fewer bugs, FP, referential transparency, everything being an expression also helps for easier automated testing. It took me a lot of persistence, effort and time to get comfortable with FP after years of imperative and oop programming, I might of even be heard to say "that's too academic, you can't use that in real life" only a few years later to realize how wrong I was! For the most part as an employee, it's limited me as few employers care about such standards/quality and just want easy to hire/most popular, it's good enough let's move fast and break things. At one time I'd happily write idiomatic Java, Javascript, PHP, etc as done so for 10 years+, now I sit poking fingers in my eyes when I have to touch them. As an employer or when I've been on the recruiting side for my employer, generally, the talent pool has been a lot smaller, extremely smaller however people that have applied have generally been at a higher skill level.