I didn't see any actual spreadsheets at those links. But my point was that paradigm matters less if you use table-driven designs (TDD). With TDD you are dealing less with the issues of attaching & managing behavior to/with structures (which the article seemed to emphasize), focusing mostly on specific business logic and exceptions to rules (oddities). The majority of your app would work without writing a snippet of code (except maybe regular expressions for validation & formatting.)

Your actual code would be "dumber" and event-specific such that paradigm differences matter less. Complex associations are managed via the RDBMS so that code rarely has to manage them.

I should make a distinction between framework coding and application coding. I won't say which paradigm is "better" for the first; I'm mostly focusing on the application-side coding here.