
The bad is pretty simple, my job is running out in about a month. It was inevitable, I'm a contractor and they only have X amount of funding. Gonna have to proverbially hit the bricks.
The good was that we had a file set that absolutely had to get done by Friday AM. I was told about this Tuesday. Fortunately it was simpler than some of the nasties that I've done recently. I worked on it off and on until 5am Wednesday, my boss submitted the first data set and it bounced with like 750 errors. I noticed one minor content semantic error that I fixed and did some chatting back and forth with the Fed's help desk to try and isolate the problem, then I realized: I didn't check the Fed's web site to see if they had a later copy of the spec.
Sure enough, version 1.2 was online, and I did the development for the school-level of detail off of v1.1. The original spec was missing a field from one of the subtotals. I added the field, fixed the DTS job that takes the data from SQL Server and turns it into a text file, then copied the code and did the district and state levels. Finished around 10pm Wednesday. Emailed my boss that the files were up and ready for testing.
Woke up about 8am today, a couple of hours shy of my target. Decided to check in at work to see if he'd uploaded them and what the result was. So I power up my laptop, start the VPN connection to Phoenix, and run the remote desktop program. Doesn't connect. Since the VPN connected, most likely source was that my computer in Phoenix was powered off. I call my boss to get him to turn my PC back on and ask him if he'd had a chance to upload the files. He said (a) the building had been without power for a while, thus, my PC was dead, and (b) all three files went up without error!
::happy dance::
So I get to crawl back into bed with my wife (semi-pre-warmed) and snooze for a couple more hours, then continue expanding the documentation for this beast.
Whee!
Still, it was amazingly cool to turnaround a three-level set of files in two days!