This post originated from an RSS feed registered with Agile Buzz
by James Robertson.
Original Post: Evils of OO?
Feed Title: Cincom Smalltalk Blog - Smalltalk with Rants
Feed URL: http://www.cincomsmalltalk.com/rssBlog/rssBlogView.xml
Feed Description: James Robertson comments on Cincom Smalltalk, the Smalltalk development community, and IT trends and issues in general.
This article by Uche Ogbuji purports to talk about post-OO development - i.e., that "moving beyond" OO is a good thing. I'm not arguing with his idea; what I'm curious about is what he means. For instance:
I think the stronger argument is that even when I think my designs were well considered, I could have done things better with dynamic, declarative and data-driven (D4) methodologies, mixing in OO in small doses only where it is clearly the best model. Aside: In my struggles to find good terminology for my recent thinking, "D4" == "Agile programming" == "Post-OO", where agile programming is not the same thing as agile process, such as Extreme Programming (which can be used with non-agile programming languages such as Java).
That's full of buzzwords, but pretty much bereft of any meaning. I'd be interested in his point, if he'd actually make it...
Previous Topic
