I started a job with the White House about two and a half weeks ago. (For you federal government geeks, it’s via an assignment from the GSA, which in turn is via an IPA from UVA.) The plan is to take the train up to D.C. once a week, and work in Charlottesville for the rest of the week. I have waited this long to write about it here because I’ve been hoping that I could write the work that I’m doing, because I think it’s interesting and exciting. But the specifics of my project are still confidential, and are likely to be for at least another few weeks, and I don’t think it’s fair to wait that long to say anything, since it affects what I’ll be writing about here. Suffice it to say it pertains to open government technology.
The effect of this is that I will not be blogging about partisan politics for the duration, and generally avoiding political matters. Nobody has told me to do this, or even suggested it obliquely. It’s no in way a requirement of the job. But I think it’s the right thing, for one simple reason: I don’t think I can write honestly about politics if I’m going to make my living working for the president. I could try, but I don’t think I could avoid bias, no matter how convinced I might be that I was exhibiting none. I have restricted my writing accordingly for the past two weeks, and I’m more or less happy with the balance that I have struck.
Oddly, this doesn’t conflict with my other new line of work, as a John S. and James L. Knight Foundation News Challenge Fellow, building The State Decoded. That’s because my $160,000 grant hasn’t actually arrived yet and, based on the paperwork that I got in the mail today, it looks like it won’t for another couple of months. So The State Decoded remains an evenings-and-weekends project for me (though less so with this new job—the folks at the White House work all the time, and I’m just trying to keep up) until I complete this project and return to my prior commitment with the Knight Foundation.
I’m having an adventure.