"Wordiness" is no the only thing that makes this article confusing. The authors zealotry <g> makes it even harder to wade thru...

Instead of giving a "holier than thou" talk, try pointing out some of the reasons why this particular design was used and is used today, and how it can be abused, and not abused...

Code tables (MUCK tables...ahhh give it a rest) can be (and have been) an elegant solution to specific design issues... 

Hierarchical data has always and will always be around, the author of the piece painted a very narrow minded "take" on it...

Next time, add some facts to your diatribe...

Cheers