Skip to main content

What can you do with $190 Billion (yes billion)?

No this is not the plot for the next Austin Powers movie. That's the amount the SecDef is asking for to keep fighting the war in Iraq and Afghanistan. And that's just the 2008 budget, which you know they'll exceed and come back to ask for supplemental funding around next June. This will bring the total amount spent on the 2 wars to $610 billion over 6 years.

Now you may say, so what? Let me put it these terms

* $190 billion in 2008 means $63,093.59 for each American
* $610 over 6 years mean $337,606.05 for each American

So let me ask you, what do you think you could have done with $337,606 over 6 years? Or, even better, can you use an extra $63,094 next year? Don't even try to compare that to the miserly 2-8% salary action your boss gives you.

All calculations based on US population of 301,139,947 (July 17th 2007 est)

Finally, to those who think I am a Bush hater, weren't we promised the Iraqi oil money would pay for the war? hmmmmm

Comments

Popular posts from this blog

The Teenage Years Cometh

If you're lucky, a few days after your twins are born, the hospital just let's you walk out with them. In fact, they insist you take them with you. No training, no classes, no probation...they really just let you walk out with 2 humans. #fatherhood — Tundey A. (@realtundey) November 28, 2021 This was me 12 years ago: And now look at them. In a little over 6 months, they'll be teenagers!   Every time I look at them, I am reminded of Obama's quote on being a parent:  "One of my favorite sayings about having children is it's like having your heart walking around outside your body." — @POTUS — White House Archived (@ObamaWhiteHouse) October 21, 2015

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 h

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 sanity First, 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