How's the Day Job?
I haven't mentioned a lot about my latest client. Frankly, I really haven't had a pressing reason to. Not that it's a bad client...I just haven't run into a lot of issues that truly stumped me beyond all hope and left me crying in a corner, tucking my knees under my chin, softly saying to myself between the sobs, "it's OK, it's OK, it's OK, you're not a bad person, you're not a bad person, just put the blanket over your head and it'll all work out."
Well, that's never happened at any consulting gig that I've been at, but one thing I've learned being a father is babies really like it when you embellish and exaggerate stories, and it's starting to happen when I talk to adults. Go figure.
Anyway, for the last 2 to 4 weeks I've been working primarily with 2 other developers, trying to get our service to match the RPS (request per second) that the customer
pulled out of his ass requested based on solid research. We pulled, tugged, and tore at the code to make it go faster, but it just wouldn't budge. Finally, we resorted to a queuing strategery, and now our service cranks like a mo-fo. It's been interesting work and I'm extended until the end of the year so I'm hoping we can start using .NET 2.0 real-soon-now as a lot of the stuff we're implementing will (literally) go away, or at the very least, become a lot easier to implement. Besides, I think the project lead is sick of hearing me say during our coding sessions, "You know, if we were using .NET 2.0 (and now 3.0), we'd be done 5 minutes/hours/days ago," so the sooner we can move to the latest and greatest, so much the better.
* Posted at 09.27.2005 11:22:48 PM CST | Link *