I just seem to grok controlling information better as tables than as programming code for the most part. Tables are like the rolls of punched paper in player pianos: you don't have to grok how the piano works to see the tune.
You have an advantage on me, then. I can't read piano roll notation. I tried it in a sequencer several years ago; nup, couldn't do it. So I found another sequencer that works entirely in manuscrupt.
So I suggest you might want to be more upfront about not grasping OO thinking. A hot "I can't understand it, so it sucks!" is rather less effective than a "I'm sorry, I don't get it - no, don't bother explaining, it's okay" or an "It still doesn't really make sense; have I got this bit right? ___", depending on what you're fishing for.
Wade.