I like how this article just ignores the role management plays in the development process. If your codebase is becoming increasingly spaghetti, and management d

I like how this article just ignores the role management plays in the development process. If your codebase is becoming increasingly spaghetti, and management doesn't let you take time to do meaningful refactoring because you gotta push out deliverables, apparently in FP this just...doesn't happen? I also like how the author says that Toyota's bad acceleration and Boeing's 737 MAX were victims of spaghetti code, therefore it must be OOP, but provides no sources to prove that these codebases even were OOP, much less that being FP would have helped prevent these errors in any meaningful way. There's so much restated information, this article is at least twice as long as it needs to be.