Dodging the BRAC bullet...

Today I found out that my job will not be moving to Millington, TN after all. I never got around to doing any BRAC posts making the case for why moving the IT functions at my command would be a really, really bad idea, especially since the infrastructure would be staying here anyway. I wasn't even sure if it would be appropriate for me to post about it, but I figured that blogging about it would be no different than writing a letter to the editor or something. Nevertheless, I only posted about this situation once before.

After the deliberations, the BRAC list that they come up will be sent to the President by September 8. He will either approve or disapprove it by September 23. If he disapproves it, the BRAC Commission has to make changes and resubmit it. Here is a FAQ that tells how the whole process works.

Anyway, needless to say, I'm very relieved. Thank you to everyone who prayed about this situation.

Appropriate for Friday the 13th

The big news today, of course, is the release of the BRAC list. What does this mean for me? It means that they may move my job to Millington, TN. Or they may not. I guess I'll find out for sure in a few months.

I've been through this before. The first command I worked at (I started as a co-op) was closed in a BRAC in the early-nineties. I found another job at another command before it actually closed. Then I got a much better job at my current command almost six years ago.

One thing for sure...I'm not moving to Tennessee -- I can't. My command can simply kiss all my training and corporate knowledge goodbye. If the worst happens, I may try becoming self-employed and go into web-design or something.

The worst part is that for the next few months, I will have to hear all kinds of doom-and-gloom, gossip and speculation about what is going to happen. When you don't know for sure what's going to happen, I guess you have to fill in the gaps somehow.