Skip to main content

Why are *you* on the Obama bandwagon?

As a realist, I know even though I don't like it Obama is going to win the nomination. But I still haven't found an Obamite that can tell me exactly why he/she is on the Obama bandwagon. Without using the words "cool", "young", "hip", "change washington" or any such nonsense. It just seems people are on the bandwagon (and yes it is a bandwagon) because
  • they think Obama is cool and all the cool people are with him (Jimmy Carter, college students that don't know electoral college from community college)
  • they realize Obama is gonna win and it's better to hitch your trailer to a winner (e.g. John Edwards)
So, tell me, why do you love Obama? Why do you think he's the best democratic candidate when he can't even win states that democrats, traditionally, must win in general elections?

To me this is how I see it: Obama is a risky choice since he can't win the "blue" states. You can preach all you want about a single America but to win elections in this country: you've gotta carry the states of your party, steal some from the other guy's party and hope the independents and old people don't confuse you for Nader. So fair or not, hopeful or not, there's a clear path that each party's candidate must take to get the required number of electoral college votes (of course it helps if your father has pals in the supreme court that can swing things your way. that's the ultimate joker.)

Clinton has demonstrated that she can win using the tried and true democratic path (after all she won the big "blue" states).

Obama is saying to hell with all that tried and true formula. I am writing my own rules. I am going to contest in every state and run a true national campaign. None of that blue state, red state for me.

So the question for you, as a voter, is are you willing to take a chance with Obama? Or will you go for the tried and true formula?

Of course, with Obama racking up so many super delegate endorsements you may not really have a choice!

Comments

Popular posts from this blog

InfoPath & SharePoint (Part 1)

A departure from sports and politics. This one is about technology.

InfoPath sucks and SharePoint is the most expensive piece of crap ever. InfoPath, as a development environment, has absolutely no redeeming value. It's worthless and if your boss ever thinks of using it, you have three options:

convince him not to (not easy once he's been brainwashed by the Microsoft marketing presentations)use one of Al Gore's lockboxes to store away your sanity 'cos you'll lose it. Also, pad your estimates very generously. You'll need every bit of time you can get.
quit immediately while you still have your sanityFirst, InfoPath:

To me InfoPath is like programming in assembly language. Sure it makes it easy (too easy in fact) to bind data to controls. But it doesn't provide you with easy access to your controls. Why is this important? Say you want to disable a button:

in most technology: buttonA.enabled = false (or something similar).

In InfoPath, you simply can't do this.…

Does InfoPath (still) suck?

A couple of years ago, I wrote a blog post titled "InfoPath & SharePoint (Part 1)". Back then I had just started working on a project using InfoPath 2007. So, expectedly, the post wasn't very complimentary to InfoPath (or SharePoint). In fact, I said:
InfoPath sucks and SharePoint is the most expensive piece of crap ever. InfoPath, as a development environment, has absolutely no redeeming value. It's worthless.... (more)Since then my opinion of InfoPath has changed slightly. It still suffers from all the flaws I pointed out in that post. However, I think when used right, InfoPath can be an OK tool. I think it's well suited for designing one off forms and not for anything that requires complex logic or multiple iterations (like most software development requires). Alas, most CTOs fall in love with its point & click simplicity and integration with SharePoint that they try to use it to replace more developed technologies like ASP.NET. What do you get? A horri…

Technical Certifications are worthless

Technical certifications, especially in the IT field, are totally worthless. Why? All a technical certification prove is that you were able to buy a couple of exam prep books, cram them in a week or two and take an exam. My monkey (if I had one) could do that. I can't tell you how many times I have interviewed certification-carrying candidates for open positions at my company only to find them severely lacking in thorough understanding of computer science. I don't care that you have an MSCD or MCP or whatever it's called these days if you don't know foundational concepts in computer science and database design.
For example, I don't want someone who just knows that you store things in a hashtable using keys. I need you to know why a hashtable is better than an array in some cases. I need you to know when an interface is better than an abstract class; when to use recursion; the different kinds of joins and when to use each one; I need you to understand how crucial sou…