Skip to main content

Post-Mortem

I try to avoid religious diatribes. I recognize that religion is an intensely personal matter, and I can remember when people would canvas door-to-door, interrupting my family during dinnertime growing up.

I also try to avoid political discussions. In my opinion, people either take a "half interested" view of politics or are rabid fanatics of everything that goes on in Washington D.C., their states, and their locales. Politically induced rabies tends to induce blindness and a general lack of common sense in people too, which is the reason why I avoid it. (I'll leave my general loathing of politicians and the tendency of them in general to put personal interests above the good of the people; lobbying ['nuff said]; and related topics out of this discussion.)

Still, Tuesday saw the biggest swing in Congress since the 40's so it is my civic duty to comment: I'm glad it's over.

I realize that the Republicans felt the need to recapture Congress given the trouncing they experienced 2 years ago. And since they were neutered and unable to advance the agenda that they felt would best serve their constituents, this does have some degree of importance. And so I get the attack advertisements and general mudslinging since, in the modern day where Snooki's Trash Talking is considered "exciting TV," this is the only way to get people's attention.

Disclaimer: I'm not Republican or Democrat. When I registered to vote, I listed myself as "Conservative," which I suppose makes me closer to being a Republican than a Democrat but I am technically neither. I believe strongly in showing compassion to one's neighbor ("Love thy neighbor as thyself.") but also have a strong sense of fiscal self-responsibility that I firmly believe should apply to government as a whole.

Having stated my personal position and my understanding of the Republican Party's need to reclaim the majority, I will say that their behavior collectively over the past few years is despicable. It is one thing to wait for the other side to make mistakes that you can capitalize on during the next election cycle. But it is another thing entirely to sit back, criticize, aggressively block any Democratic action on the grounds that the Democrats are for it "so therefore we must be against it," and generally act like a 1st grader in the sandbox who is pissed at the schoolkid next to you because they started playing with the Tonka dumptruck that you were eyeing.

So I'm glad this is over. The country has suffered from Wall St. for sure, and I haven't been shy in lambasting the pigs in the Financial Services district (and that includes the shady mortgage dealers too) for bringing this country to the brink of ruin, but I expect better from a Congressional body that is supposedly elected "by the people and for the people."

Here's to the next 2 years, which will hopefully be better because Congress is able to focus on what they should be doing: representing the American People.

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