Glad we cleared that up:
White House Press Secretary Jay Carney announced during Thursday’s briefing that Attorney General Eric Holder sent a letter to Senator Rand Paul (R-KY) this morning regarding the administration’s policy on drone strikes targeting Americans on U.S. soil. Holder’s letter stated definitively that the U.S. would not use “weaponized” drones to targets American citizens on domestic soil.
Reading directly from Holder’s letter to Paul, Carney said, “Does the President have the authority to use a weaponized drone to kill an American not engaged in combat on American soil? The answer is no.”
Well, that's a relief. I was worried we'd repealed the constitution.
I may have more about Rand Paul's filibuster and John McCain's complete failure to understand its significance later.
That's the problem. People inhale and exhale mentally, and right now, I'm exhaling. This means I get a lot of work done, but not a lot of reading. This, in turn, means more lists like this:
Lunchtime!
Principally, it means not having to commute in 15 cm of snow. It also means several uninterrupted hours of working on stuff. And, unfortunately, not reading all this yet:
Now to walk Parker in the snow, and keep working...
Netsch was Illinois' first female nominee for governor and the Illinois controller in the 1990s. She died this morning at age 86 from complications from ALS:
She was one of the first female law professors in the United States. A liberal Democrat, she defeated the Machine-backed incumbent state Sen. Danny O’Brien to win a seat in the Illinois Senate in 1972 that she held for 18 years. Elected comptroller in 1990, she was the first woman elected to statewide office in Illinois and, four years later, the first to run with the backing of a major political party for governor, losing to incumbent Gov. Jim Edgar.
Netsch said she “never ran as a woman” but always argued, “More women are needed to make a difference in public policy.”
“She paved the way for others,” President Barack Obama wrote in a letter read at the event by former senior presidential adviser David Axelrod. “The unwavering grace and integrity [Netsch] has shown throughout decades of public service are an inspiration to us all. Dawn’s legacy will live forever in our hearts and the history books.”
I volunteered for her 1994 gubernatorial campaign against Jim Edgar. I remember the campaign, especially how excited we were to work for her. We didn't even come close in the general election—Edgar got re-elected with 34% of the vote—but we thought we made a difference. We might have; Edgar and his successor, George Ryan, were moderate Republicans who resisted the creeping Christianism of their parties.
She will be missed. If Illinois native Hillary Clinton gets nominated for president in 2016, she can, in part, thank Netsch for the example.
Exhibit 1, yesterday at 4:58pm:
I don't know what to do with myself the rest of the day. I've just deployed the completely-redesigned Weather Now application. I feel 10 kilos lighter.
Check out the preview on Windows Azure.
The application started in mid-1997 as a feature of the now-defunct braverman.org, my proto-blog. The last major changes happened in 2006, when I gave it a face-lift. I've occasionally pushed some bug fixes, but really, until today it has looked and acted essentially the same way for 6 years. (The GetWeather application, which downloads and parses data from outside sources, hasn't changed significantly since 2002.)
So what's new? In sum:
- The application now runs on Microsoft Windows Azure, up in the cloud. (Check out the preview!)
- This means it also runs on Azure SQL Database instead of on-site SQL Server.
- Since I had to port the database anyway, I completely re-architected it.
- The database rearchitecture included moving its archives to Azure Storage, which will pay benefits once I update the UI to take advantage of it.
- The ancient (1997, with revisions in 1999, 2002, and 2005) GetWeather application, which downloads weather data from outside sources, got rebuilt from byte 0 as well.
- Finally, I fixed 35 bugs that the old architecture either caused or made fixing overly difficult.
There are a few bugs in the preview, of course. This morning I found and fixed 6 of them, all related to architectural changes under the hood that the creaky user interface didn't understand. And just now, I discovered that it thinks the sun never shines anywhere—again, almost certainly a problem related to changing from using the broken System.DateTime object to its replacement, System.DateTimeOffset. Always another bug to fix...
Still: I'm done with the port to Azure. I'll bang away on it for the next week, and if all works out, on Saturday I'll finally, finally, finally turn off my servers.
James Fallows has a thoughtful piece looking back at the start of the Iraq War, ten years ago this month:
Anyone now age 30 or above should probably reflect on what he or she got right and wrong ten years ago.
I feel I was right in arguing, six months before the war in "The Fifty-First State," that invading Iraq would bring on a slew of complications and ramifications that would take at least a decade to unwind.
I feel not "wrong" but regretful for having resigned myself even by that point to the certainty that war was coming. We know, now, that within a few days of the 9/11 attacks many members of the Bush Administration had resolved to "go to the source," in Iraq. Here at the magazine, it was because of our resigned certainty about the war that Cullen Murphy, then serving as editor, encouraged me in early 2002 to do an examination of what invading and occupying Iraq would mean. The resulting article was in our November, 2002 issue; we put it on line in late August in hopes of influencing the debate.
My article didn't come out and say as bluntly as it could have: we are about to make a terrible mistake we will regret and should avoid. Instead I couched the argument as cautionary advice. We know this is coming, and when it does, the results are going to be costly, damaging, and self-defeating. So we should prepare and try to diminish the worst effects (for Iraq and for us). This form of argument reflected my conclusion that the wheels were turning and that there was no way to stop them. Analytically, that was correct: Tony Blair or Colin Powell might conceivably have slowed the momentum, if either of them had turned anti-war in time, but few other people could have. Still, I'd feel better now if I had pushed the argument harder at the time.
Almost done publishing the first beta of the new Weather Now. If it's successful, I'll post the link tomorrow.
I've just finished—I mean, finished—the Weather Now worker role. The worker role runs in the background and performs tasks like, for example, downloading the weather from outside sources, parsing it, and storing it.
I have three tasks left to enable me to publish the new version of Weather Now to its new home in Windows Azure:
- Create a script to initialize the lists that appear on the site's home page;
- Upgrade the existing ASP.NET website to an ASP.NET web application; and
- Create an Azure Cloud Service Web role to house the application.
I believe I will be done today sometime. But first, Parker is demanding a trip outside.
I'm just a day from losing my mind (or "loosing," to all you Facebookers out there), a day from my workload returning to normal levels, and a day from deploying Weather Now to a test instance in Azure. Then, maybe, I'll have time to take all these in:
Watch this space for a sneak preview of Weather Now 4.0, possibly tomorrow. The GetWeather utility has run with only minor hitches for a week, and with two more (quick) bug fixes it's ready for production. That just leaves about 6 hours of work to move the ASP.NET application up to Azure...and then, you get to beta test it. If all goes well I'll cut over to Azure on the 9th or 10th, and finally—finally!—retire my last two servers.
After a couple of days in which I'm glad we keep bourbon in the 10th Magnitude office, Scott Hanselman's examination of working remotely seems timely:
I see this ban on Remote Work at Yahoo as one (or all) of these three things:
- A veiled attempt to trim the workforce through effectively forced attrition by giving a Sophie's Choice to remote workers that management perceives as possibly not optimally contributing. It's easy to avoid calling it a layoff when you've just changed the remote work policy, right?
- A complete and total misstep and misunderstanding of how remote workers see themselves and how they provide value.
- Pretty clear evidence that Yahoo really has no decent way to measure of productivity and output of a worker.
All this said, it's REALLY hard to be remote. I propose that most remote workers work at least as hard, if not more so, than their local counterparts. This is fueled in no small part by guilt and fear. We DO feel guilty working at home. We assume you all think we're just hanging out without pants on. We assume you think we're just at the mall tweeting. We fear that you think we aren't putting in a solid 40 hours (or 50, or 60).
Because of this, we tend to work late, we work after the kids are down, and we work weekends. We may take an afternoon off to see a kid's play, but then the guilt will send us right back in to make up the time. In my anecdotal experience, remote workers are more likely to feel they are "taking time from the company" and pay it back more than others.
I like working from home when I have a lot of creative or intense work to do, but generally I prefer working in the office. I've also been thinking about the compromise solution of moving to within, say, 500 meters of the office, so I can get home in 5 minutes if I need to.
Meanwhile...back to work.