Walking Obama Back
Yesterday’s New York Times had one of those “Washington Insider” stories wherein presidential advisers express dismay of pants-peeing proportion that the guy in charge actually said what he felt about a morally troubling issue. Time to get him back in the box.
Here’s the President’s quote from an earlier NYT article:

Syria and Chemical Weapons
“We cannot have a situation in which chemical or biological weapons are falling into the hands of the wrong people,” Mr. Obama said in response to questions at an impromptu news conference at the White House. “We have been very clear to the Assad regime but also to other players on the ground that a red line for us is, we start seeing a whole bunch of weapons moving around or being utilized.”
Our foreign policy uber wonks would have Obama apparently follow Bill Clinton’s example (and crushingly poor judgement) in refusing to acknowledge that what was happening in Rawanda was genocide. Clinton administration officials declined to even use the word “genocide” as they might have to actually do something if they did.
Obama said what he thought and felt but here is how a “senior official” spins it now, “Mr. Obama was thinking of a chemical attack that would cause mass fatalities, not relatively small-scale episodes like those now being investigated, except the “nuance got completely dropped.”
Now we get it. The occasional use of nerve gas where a dozen or so are killed and injured: not a big deal. By that calculus the Boston bombing was not even front page news. But, of course, we apply a different formula for non-US terror casualties.
It must be admitted that this is all muddled by the memory of George W. Bush engaging in a ground war in Iraq over specious claims of weapons of mass destruction.
But if American strategic interests demand our constant involvement in the Middle East to protect our 51st state (Israel) and our dependence on oil, the President should at least feel free to be morally indignant about the actual use of a chemical weapon without his staff swooning in confusion and fear.
After all, a president being honest is a nice thing–every once in a while.













The DC press was all over a recent incident where a Metropolitan police motor officer was struck and injured by an auto while stopped in far southeast DC, close to the border with Prince George’s (PG) County, Maryland. No DC ambulances were available and the officer was eventually transported by a PG unit after one was requested.
The “wait time” issue is thorny, complex and longstanding. This is just one example. DCFEMS Chief Ellerbe seems to want to run the department as if it were a business: staff to meet the demand. If you ran a clothing store and 90% of the customers came in from 5PM to 9PM, you wouldn’t have 90% of your employees working in the morning. They would show up at 5PM. This is hardly rocket science but it is a big change for the department. And, there will be times when an ambulance is not readily available, that’s why we have fire companies with EMS (including Advanced Life Support) capability. That’s also why automatic mutual aid is essential.
At the end of the day, the Department (and the union) is made up of a variety of folks with their competing agendas. It would be nice if it were a sure thing that Local 36 was interested in the welfare of the citizens but I am not sure that is the case. As an example, this past New Year’s Eve, 100 folks called in sick resulting in 12 ambulances being placed out-of-service. According to a local media outlet, “one man died from cardiac arrest while waiting for an ambulance on New Year’s Eve.” Some ascribe this to firefighters being pissed off about not receiving holiday pay on Christmas Eve.


































