Exactly, like thousands of other companies we have unique systems we have to develop in house.

Mmmm...I had mussels about 10 minutes ago with wild Coho salmon kale for dinner (a 10 minute meal). Just steamed em with white wine, bay leaf, lemon juice, garlic.

I'm a developer for a company with a single location, a small transaction volume (30/day), a few vendor and in house apps (.Net/Oracle mostly), and an unlimited IT budget. Our business users are unhappy at how long it takes us to deliver apps, and how often our projects "fail". The reasons seem to be that: a) Our architect won't allow us to develop single layer apps ("what are you, pro-silo?"), instead each must be broken down into a variety of service layers for some future "reusability" that must be distributed across various servers. b) MS is making it harder and harder to code out these layers, by for example replacing .asmx web services with WCF technologies. The problem could also be c) Incompetent developers, but it sure seems like MS' former focus on high level simplicty and business productivity has evaporated. Is RAD even possible anymore? Thanks.