I don't really believe this but ok. I worked at a functional / typescript heavy shop where when I had parsed what a complicated set of steps was doing discovered multiple redundant queries and a library that was parsing strings into code. But damn some of those functional paradigms chef kiss /s. Imo my dumbass code , besides being demonstrably more performance was way less of a liability.

Your argument is "I once saw someone do stupid FP, and it is all I have seen. Therefore, I believe all FP is stupid."

Sure, replace functional/generics/static typing with your poison of choice.

Just remember that, at some point, the "dumbass" thing was pushing sticks into clay tablets.

Functional programming may not be the future. But dismissing other's code because it is not done "the way we are used to" is stupid.

> I worked at a functional / typescript heavy shop where when I had parsed what a complicated set of steps was doing discovered multiple redundant queries and a library that was parsing strings into code. But damn some of those functional paradigms chef kiss /s

And I've worked at a place where the imperative code was crap. Should we abandon all imperative code because I had that experience?

People can write bad code in any paradigm - that's not what decides how we should code.

Nobody says we should throw away all imperative code because of one poorly implemented code base. But for some reason I see that targeted at FP all the time.