No, I have seen tons of times when one developer on a single code base build a rats nest for themselves by just doing OOP.
Sure the objects or classes where probably not perfectly designed or the choices of the correct objects/classes to begin with, but that is the problem with OOP, you don't know if the main building blocks you are using are the correct ones.
Comments
He's inherited several rails codebases and has to maintain them.
Sounds like the 'other peoples code' problem to me.
Just like all non trivial abstractions are leaky (Joel) I guess all non-trivial applications are 'hairy'
No, I have seen tons of times when one developer on a single code base build a rats nest for themselves by just doing OOP.
Sure the objects or classes where probably not perfectly designed or the choices of the correct objects/classes to begin with, but that is the problem with OOP, you don't know if the main building blocks you are using are the correct ones.
So you are saying it's impossible to build a rat's nest with FP? It's problem with programmer, not with tool.
Uh? Where did I write that? Why are you making up what I wrote?
I guess your assumptions are in line with the OOP programming style... ;-)
You can make a rat's nest of any coding paradigm, however I would argue it is easier to do it with OOP.