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

"Ni jiang yi yang de hua ma?"

Last week, I wrote about the necessity of having a clear message . Because this topic is so important I decided to follow-up with another entry on this general subject. This week we will approach it from another angle. (For the curious, the title says " Do you speak the same language? " in pinyin, which is a transliterated Mandarin Chinese.) Recently, a good friend of mine (who is Chinese, ironically) and I were playing pool. He had to bank the 8-ball in the pocket to win the game, and since it was an informal game and bank shots are my area of expertise, he asked me for advice. I told him, "you just need to strike the cue ball with medium speed so that it hits the 8-ball right in the middle." He didn't believe me so we marked the positions of the balls, and then he took his shot only to watch the 8-ball sail past the pocket. "A-ha!" he exclaimed. "I told you it wasn't that easy." But when we reset the positions and I made an attemp

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 that

Is No/Low-Code the Key to IT Nirvana?

 Unless you've had your head in the sand for the past year or so, you've seen the phrases low-code  and no-code  bandied about quite frequently everywhere you look.  You've probably wondered if this is something new that's here to stay or just a "flash in the pan."  Although the terms have been in the fore of the IT trade publications recently, Low Code Development Platforms (LCDP) (and the corresponding No Code Development Platforms) have been in existence since 2011.  Their roots can be traced to the 90's with 4th generation programming languages and GUI-assisted programming paradigms, e.g. IBM VisualAge for Basic, which was discontinued in 1998. For those of you who aren't familiar with either, the premise is that these platforms allow someone to quickly build applications using a WYSIWYG interface and a "click and configure" paradigm to Isn't this the source code to Roblox? rapidly build full applications with little or no coding requ