I agree with this. I don't think it makes sense to be "oop" or "fp". Different problems have characteristics that lend themselves to different techniques. Di

I agree with this. I don't think it makes sense to be "oop" or "fp". Different problems have characteristics that lend themselves to different techniques. Difficult code based come from purists who value theory over practicality. I have a very strongly enforced "don't be clever" rule for teams I manage. Code should read like a story, good code reduces congnitive load. I've seen some chains of map, reduce, filter, etc... written by FP purists that are difficult to decipher. Good code is a love letter to the next developer.