- Apr 27, 2015
Interesting take on OOP. I have lived some of his views while trying to tame the monster I inherited. I found myself rocking back and forth on simple issues as far as where to put the code (should I make a separate Module, should I put it in the Objects Class, do I make a "Utilities" Module, etc) instead of simply "just doing it". His metaphor about individually wrapped candies was spot-on!
All that being said, the true nature of this video really doesn't apply to most of us on this forum. A huge percentage of our coding is done within forms and reports which forces us to comply with OOP to some extent.
To a non-programmer such as myself, Access's code-behind-the-forms paradigm was a God-send. All of a sudden I could do cool things without having to take a butt-ton of CS courses and invest in pocket protectors.
Funny thing is, my first introduction to databases was with Paradox/PAL, which at the time was a break from traditional programming (or so I was told) but to really do anything spectacular with it, you had to write whole procedures.
When Windows 95 became the norm and subsequently MS Office, I rebeled against the machine and went an RDBMS strike until I was forced back into it in 2008. By then Paradox and all other RDBMS apps were marginalized and Access stood alone at the top.
I held my nose and started to learn it and after awhile I decided it didn't really smell all that bad and when Access became the reason for my employment a year ago, it smells 'purt damn nice.
Anyway, now that I have made this all about me, thanks for the video. It is refreshing to see different POV's on things.
Edit: On reflection, unless I missed something, the speaker never really spoke to the actual performance of OOP in relation to the other methods. Only the readability and other aesthetics. Hardly a solid platform to sell your case on...