Coding Confessional

Anonymous Confessions from Programmers.


Absolutions: 18 • Condemnations: 9



Anonymous #1:
Forced OOP is unnatural. I start with plain functions. Once I get something up there, I ask myself "would this be better if I turned some things into classes?" Usually, the answer is a definite "no". That approach cuts out a lot of bullshit.
Anonymous #2:
It depends on what language you're using I guess.
Anonymous #3:
OOP is a failed experiment. Don't feel dumb OP.
Go functional, then you will feel idiotic
Anonymous #4:
8 years whole years ? OK, I agree OOP is mostly bulshit because it's used where it shouldn't be used. 8 years of experience doesn't mean anything!
Anonymous #5:
imo OOP is really only useful when the abstraction is explicitly "I'm tying this kind of functionality to this data in this scope." When used only as a grouping mechanism (e.g. as a glorified map or just to provide a graphable schema), it's usually pretty meh compared to what any old typing system would give you.
Anonymous #6:
+1 for Anonse #1. The best approach to writing code. OOP is the most overrated paradigm. Best way is to use it as last resort, when there's no other clean way to implement it. Code being put in one class is ones of the strongest couplings you can do, that's why it should be only used as a last resort.
Anonymous #7:
"OOP" was easily the most-over-hyped paradigm, far more than FP is today... Really, just an accident of history. Java 1.4/C# 2.0 style "OO" is more like "thing-oriented" programming ("design patterns" exist to cover missing language features) and dovetailed with two-tier/table-driven apps UML bullshit and "rapid development" like ADF/VBA just enough that your manager could "understand" it, which is all it took to fuel a publishing craze and ruin a generation's worth of applications.