not very nice wording, if you ask me
but I have experienced similar environmental issues in my own life. Wade's description fits patterns I have observed; I trust his analysis and conclusions more often than yours as a rule.
A more diplomatic way to say such may be something like, "His thinking style and experience seem to better match my own than yours".
My techniques work (at least if you think like I do). Tables are objectively more compact information-wise because they use context instead of localized attribute labels/methods to specify what an attribute is. And, I think most would agree that one can see more row-wise and column-wise patterns in attributes as a table than as a bunch of linearized class attributes or XML. I am simply applying these universal truths to software development. Plus, one can do relational algebra and other table-browser tricks on tables to customize your view of the attributes. You are not stuck with Bill Gates' or Gozling's view of the friggen code. TOP gives me the freedom to see bunches of attributes as *I* want to see them, filtered row-wise, column-wise, and join-wise how I want. I become the master of my working domain, not Gozling. It seems so obvious to me. Why most of you want that tangled, static, linearized, 60's navigational-DB-style mess, I have no friggen idea. You people have weird brains. I better clone myself 100 times before more OO and array heads reproduce and kill off the last table fans.
