There are many such posts (explicitly theoretical/academic) in the site's history. More importantly, the day to day "McMansion" posts actually back up the theoretical concepts expressed in such posts. Much the way we programmers use both positive and negative examples of Design Patterns.
If you are not aware -- and it seems like you aren't -- the Design Patterns movement in software was inspired by an architecture book that did much the same thing -- showing patterns and anti-patterns -- just with less hipsterism, and more examples than counterexamples.
Lol I don't believe it's worth my time to argue this further, since you haven't made any actual arguments, and you come off as kind of a jerk with all the unsupported claims, not responding to my points, and demanding that I do work for you. Sorry you are blind to this. If you want to understand your deficiencies in this area I'd recommend reading A Pattern Language by Christopher Alexander, followed by Design Patterns by the 'Gang of Four', then thinking about the connection between architectural pattern languages and cutting edge software design. Perhaps think about why programmers have taken the time to assemble libraries of anti-pattern examples specifically, analogous to McMansion Hell's.
http://mcmansionhell.com/post/161514422581/mmh-does-architec...
There are many such posts (explicitly theoretical/academic) in the site's history. More importantly, the day to day "McMansion" posts actually back up the theoretical concepts expressed in such posts. Much the way we programmers use both positive and negative examples of Design Patterns.
If you are not aware -- and it seems like you aren't -- the Design Patterns movement in software was inspired by an architecture book that did much the same thing -- showing patterns and anti-patterns -- just with less hipsterism, and more examples than counterexamples.