Skip to main content

How Do I Say I'm Sorry?

Similarly to last week, I was so floored by one article (blog entry, in reality) that I have to rehash it here. No, I'm not being lazy. But it is well-known to my readers that I'm not against biting the hand that once fed me, especially when that hand belongs to the Captains of Cash (which is a lot nicer than some other names you and I could have devised).

In the blog entry, it examined some of the statements made by these Titans of Treasure in light of the housing crisis and provided their total compensation (salary, bonus, options, and retirement benefits) as a means to see how beneficial it is to be someone who feels "it is better to beg for forgiveness than to ask for permission."

So how much does an apology cost? USD$2.3 billion dollars.

Yes, that's billion with a "b."

Ideally, I'd like to figure out the total years these gentlemen worked collectively as the heads of their respective institutions to determine a cost per year, but a) it's Monday morning, b) I'm lazy, and c) when you're looking at a total figure that large, the cost per year really doesn't matter.

In honor of these Generals of Gravy, my favorite job to have is no longer a meteorologist, where you can be wrong 75% of the time and still receive a 6 figure salary. It is now a CEO of a financial services institution where I can be wrong 50% of the time (or at least wrong when I'm telling the public about my firm's record-breaking profits..."If this is wrong I don't wanna be right!") and make an 8 figure salary.

One of these days, I'll tell you why I think it was wrong to repeal Glass-Steagall (if you don't already understand the history behind it and its implications), and why I am ecstatic over the efforts of Senator Blanche Lincoln and (gasp!) President Obama to impose huge restrictions on the sale of complex financial instruments. The huge irony here is that I consider myself to be more Republican than Democrat, but my political leanings are most definitely trumped by my fiscal attitude, which has been conservative for quite some time.

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...