One thing in this article I do agree with is that you should try to write "as little code as possible". But it doesn't follow that if you don't know how to code

One thing in this article I do agree with is that you should try to write "as little code as possible". But it doesn't follow that if you don't know how to code, you'll write zero code, and do well by that metric! You'll be unable to identify people who can code well, and hire poor coders to solve your problem, ending up with lots of low-quality code, in situations where an experienced programmer could have come up with a better solution ("hmm, I've seen this before..."). Even the slightest familiarity with programming here will help someone understand that when an offshore development house says "oh, sure, we'll just throw 20 more people at the project", that will not necessarily make it done better or faster. This is a Good Thing. And this has nothing to do with whether or not Mr. Bloomberg is implementing his own Ruby or .NET scripts.