3 ms·
>> [OOP] can backfire badly if coders end up doing simple things in complex ways just because they can. Very true. I'm taking several courses where the vast ma
by TallGuyShort 17y ago
>> [OOP] can backfire badly if coders end up doing simple things in complex ways just because they can.
Very true. I'm taking several courses where the vast majority of students have only been exposed to Java, where as I've come from a C background with experience in several other languages. I'm shocked at how the other students have no sense of efficiency or simplicity - everything has to be about making other classes do the work, and it ends up being a horrible project.
- javanix 17y agoI think the trouble with teaching mostly Java-only courses early on in CS curricula is that it makes it difficult to catch the subtle middle ground where OO actually makes code more readable/maintainable instead of more bloated. Granted, a lot of that comes from experience in OO languages, but I think using C or another language helps people see that middle ground a lot easier. It helps make it more obvious where OO would help and where it would just be needless obfuscation.
- MarkBuckingham 17y agoI think the whole Design Patterns thing is at fault here... People see a problem and try to figure out which DP to plug in, instead of thinking through the problem itself. Design Patterns can be a good way to think about the problem, but shouldn't be a substitute for thinking either.