10 Fallacies of Software Analysis and Design.
Man.. I swear, I could have written that article. Talk about taking the words out of my mouth.
You know, OO is nice, but procedural is nice too, and everything is implemented procedurally anyway.
Acknowledge state! Acknowledge concurrency! Acknowledge time!
The stuff on abstractions and space time just had me written all over them.
In short, I agree 100%.
The sooner people stop trying to make things simpler the sooner things will become simple.
I still struggle with how to handle feedback and resources though.
Computer science doesn't feel to me like it's where it should be.. maybe I just hang with the wrong crowd..
the day people stop trying to simplify things will be the day we stop programming.
remember that procedural programming didn't always exist. they were invented by dijkstra in the 70's. before that you had assembly and jumps and so on.
procedures are as much an abstraction as objects, and are suitable in some cases (particularly functional programming) where there is a clear multiple inputs and single output (think XSLT). for modelling a shoot-em-up game with moving state, objects really are the best abstraction.