Skip to main content

More Ridiculousness on Wall St.

After writing last week's entry, I came across an article that described something that has been going on in the marble halls of Wall Street for some time: the run-up of oil prices not by supply and demand economics but by the commodity traders on The Street who, by the mere act of betting on the future price of oil, create a self-fulfilling prophecy. This activity is not new to those who have the power to change policy and regulate these types of activity, yet they do nothing about it. To quote one of the best parts of this article...

After peaking at nearly 9.8 million barrels a day in August 2007, demand for gasoline has fallen steadily to a low of 8.5 million barrels day in February 2010 — a drop of 13 percent. But in the past 12 months, pump prices have increased more than 50 percent and oil prices have more than doubled. “People are using oil as a store of value rather than as a commodity,” Beutel said. “It’s the investors who are buying.”

Reading that should have made your skin crawl, since it is counter to everything we know about price movements, i.e. if demand falls then so does the price. Yet those on The Street once again demonstrate that they don't give a damn about the effect they have on the economy if it means they can make a quick buck.

Do not get me wrong: I do not exonerate the oil companies of their part of this. They have just as much culpability as do the traders I am writing about. But allowing this speculative activity to continue is akin to simply writing the traders a blank check, since what they are doing amounts to printing money.

Here's a message to the U.S. Government: write them a blank check and put a halt to what is happening. The end result from their perspective is the same, but I won't have to cringe anymore when I pull up to the gas pump.

Popular posts from this blog

It's Easier to Fail at DevOps than it is to Succeed

Slippery when wet Since the term DevOps was coined in Belgium back in 2009, it is impossible to avoid the term whether in discussions with colleagues or in professional trade magazines.  And during the years while this movement has gained momentum, many things have been written to describe what elements of a DevOps strategy are required for it to be successful. Yet in spite of this, there is an interesting data point worth noting: not many organizations feel there is a need for DevOps.  In a Gartner report entitled DevOps Adoption Survey Results (published in September 2015),  40%  of respondents said they had no plans to implement DevOps and 31% of respondents said they hadn't implemented it but planned to start in the 12 months after the survey was conducted. That left only 29% who had implemented DevOps in a pilot project or in production systems, which isn't a lot. "Maybe it's because there truly isn't a need for DevOps," you say.  While t...

So What is this IPaaS Stuff, Anyway?

 In my last post , I discussed how no-code/low-code platforms fulfill rapid development of business applications - addressing the needs of the Citizen Developer (a Gartner term  first used around 2009).  I also commented on how this specific objective limits their ability to provide true integration capabilities, which require the flexibility to adapt to the myriad variations of infrastructure.  This is a concern because companies often have acquired legacy systems via M&A activity while simultaneously investing in new technology solutions, resulting in a mishmash of systems with multiple ways of accessing them. In this post, I'd like to examine how the needs of the latter group are met by describing some key capabilities that are "must-haves" for any company looking to execute on a digital transformation strategy.  In order to do this, let's define who the target user base is for such a technology platform. Disclaimer:   I work for MuleSoft (a division...

Application Development Done Right

In a previous article, entitled DevOps as the Ultimate Panacea? , I described how developing code without thinking about the current needs of the end user as well as the future needs once they've become accustomed to using your application ends up not only frustrating them but also can result in customer churn and ultimately lower revenues.  In this article, I'd like to describe something simple that I came across today that shows a definite degree of effort to do quite the opposite. Recently, we had a severe snowstorm, one with blizzard-like conditions, which is unheard of in central New Jersey.  Being responsible adults, my wife and I went to the grocery store to stock up on essentials (read:  chips, chocolate, etc.) in case we get stuck at home. As we were ringing up our order, the cashier mentioned to us that the store has a mobile application.  Since both of us are in technology oriented professions, we were skeptical about the need for a grocery store mob...