4 ms·
Not convinced it's the application of OO patterns that leads to bad code but bad programmers (at least in the major part). I've seen clean code bases in OO/fun
by noir_lord 10y ago
Not convinced it's the application of OO patterns that leads to bad code but bad programmers (at least in the major part).
I've seen clean code bases in OO/functional and pure procedural and bad code bases in those as well.
I think it's tempting to blame bad code on things like bad languages and bad architectural patterns because they are externalities and can be blamed without mentioning the gorilla in the room, bad programmers write bad code.
I'm not clever so I don't write 'clever' code, I actually find it hard to work on code bases where they tried to be clever or do too much in one function/class.
Architecture is like salt, a little enhances, a lot ruins.
I don't write simple clear code out of any sense of purity or attempt to be 'clean' but because I know that in six months when I open this file it'll be me fixing it and I won't understand what the hell $me-6mths was thinking.
- FranOntanaya 10y ago> Not convinced it's the application of OO patterns that leads to bad code but bad programmers There's one thing I would point at. When non OO code is bad you can usually point at the problem: bugs, performance, security issues, coupling, so on and so forth. OO code can be bad yet contain no debuggable issues. Once it's laid out, noone is going to "fix it" because it's not technically broken. It'll just rot due to lack of maintenance, until there's noone left with a good mental map of it and enough of the non-OO contents are broken enough that it gets replaced all at once.