This was a bit of a busy week.
Tuesday I had an electro appointment. It went as well as any. I have very sensitive skin and am always noticeably swollen the day after. And I really couldn't skip work this week or work from home on Wednesday because we had a release. Thankfully, most everyone is aware that I'm high maintenance and when they saw my face on Wednesday, they just said, "Allergies, huh?!" To which I replied, "Ya."
Wednesday was a b!tch!. Working in web based software is quite a different beast from traditional software. In some ways it’s much easier because you have total control over your platform. But when you have an error, everyone see's it right away and you start getting phone calls at 6:00 AM. So getting it right the first time is crucial when your business is dealing with Fortune 500 companies data. And the VP called this release the single biggest release of our company's history. So there was major pressure to get it right.
This release was crucial in so many ways. For one, it had already been pushed back by two weeks after I brought up the fact that there was no data syncing plan between two of the new servers. And secondly, this implemented some security requirements that will enable us to get a few new financial institutions as clients (big money was on the line). So we started the release at 5:00 PM and by 9:00 PM we had come across a major bug in the OS of a $20,000 server that was 90% of the reason for this release! We spent the next 4 1/2 hours on the phone with tech support trying to find a resolution to no avail. So we pulled the thing out and dropped in a $7,000 Windoze OS machine with some stripped down features but some I/O upgrades. It worked great, so now we're going to return the other server and get our money back. We ended up working until after 4:00 AM but the post mortem revealed that no unknown bugs or mishaps traceable to our team played a factor. So our VP cleared our portion of the release with 100% satisfaction. Also, I'm pretty proud of myself simply for getting a reputation in my new position as the guy who finds the show stoppers! In each of the three releases I've been involved in since moving to this department, I've found a major show stopper in time to be fixed and before any were seen by clients. Yay for me!
On Thursday I had a doctors appoinment. I got my hormone levels checked and was quite pleased with the result. "E" count was just above 1200 and "T" count was 19. He said I was also slightly anemic so they took some more blood to do more tests. I rarely eat meat, so in the last two days, I've eaten meat for both my meals (I only eat once a day). I was also low on sodium. Another great thing was my doctor didn't make any wierd comments. In the past he had always managed to say something odd or act a little different whenever any TG issues came up. This time he was pleasant and professional. I was thinking I'd have to change doctors, but now I think I'll stay with him. Thursday night saw another brown-out! Not sure what's up with that, but being without Interschnitzel sucks butt! Hopefully they've fixed the issue permanently.
Friday was mostly uneventful. I was planning on taking the day off but ended up going in anyways. At 5:30, just as I was getting ready to head out and meet a friend, one of my bosses came into my cube and said we had to do an immediate patch to a bug that was a known issue. Apparently one of the sales guys was on the phone with the VP all day bitching about it. The QA cluster was down for a few upgrades so we couldn't test properly and before I could bitch and moan, all the senior level decision makers left the building. I was forced to make a few big decisions, which I don't like to do. Release straight to production and do a test there and then roll it back if it fails, or can the whole thing and face the wrath on my cell phone later this weekend? I decided to go for it. We did the patch, tested and told webops to standby for the next 24 hours. So far so good!