Don't you dare think I made it up. It's even in Wikipedia:
marchitecture. "Marchitecture (or Marketecture) is a portmanteau of the words marketing and architecture. The term is applied to any form of electronic architecture perceived to have been produced purely for marketing reasons. It may be used by a vendor to place itself in such a way as to promote all their strongest abilities whilst simultaneously masking their weaknesses."
Here's an article about the vendor-produced version at
it-director.com: "A Marchitecture is an architecture produced for marketing reasons, normally by a vendor. It is designed to put the vendor in the best possible light by emphasizing the positive as well as hiding the negative. If you are in marketing you will spell it Marketecture."
I give you an example, although I in no way attest to whether it's a.) true and b.) personal. Let's say you want to convince a potential customer that your product is as safe as possible. A security document may get drafted that then requires that the code (and reality) be rebuilt in order to match the claimed design. While it's good practice to incorporate security from the beginning, and agile may make security stories your priority anyway, approaching the code from a marketing decision, particularly because the marketing materials may be misinterpreted and lead to offshoots you didn't originally intend, is a frustrating path to follow.
Snarky: You'll need to recode this portion of the project. As you can see, your REST design doesn't mesh with the new marchitecture.
Title: Who the hell is Mark?
