The principles of database design, or, the Truth is out there

Seems like this article places too much emphasis on normalization, which is appropriate for many cases, but may be a huge cost and performance issue for requirements like reporting. You may probably need different kinds of schema and data storage structures for different requirements in the same application, which in turn may result in duplicated data, but results in acceptable trade offs.

Putting aside performance implications, I get kinda irritated by having to do joins for basic queries all the time.