I actually think that doing things in stored procedures could be a great hack to squeeze out some extra performance, and I'm sure that a system like this can accomplish some important business goals.
However, in the example I'm thinking of, it was much more dysfunctional. The advantage of stored procedures there was that the organization's release process was so broken that it was much faster for sales and marketing to get features added by going through Carl, the DBA, instead of submitting the request to the dev team. This was because Carl was able to add the logic by sending one query rather than going through the broken months-long release process.
Carl was actually a real nice guy, although hard to get a meeting with due to his great importance and busy schedule.
However, in the example I'm thinking of, it was much more dysfunctional. The advantage of stored procedures there was that the organization's release process was so broken that it was much faster for sales and marketing to get features added by going through Carl, the DBA, instead of submitting the request to the dev team. This was because Carl was able to add the logic by sending one query rather than going through the broken months-long release process.
Carl was actually a real nice guy, although hard to get a meeting with due to his great importance and busy schedule.