Huh? I read the article as being about simple code that is easier to understand and maintain because it's not semantically overloaded with abstractions, and pic

Huh? I read the article as being about simple code that is easier to understand and maintain because it's not semantically overloaded with abstractions, and picking data structures that fit the need of your process, instead of some patterns because Herb said so or something. Usually you don't need code samples for that because it's such a common bad thing. The ultimate data-first man would be Chuck Moore.