Yesterday was a fun-filled hectic day of work.
We have a build coming up in the next day or so and it appeared that our new framework, which was supposed to help us for future updates and the new algorithm coming down the pipe, was totally broken.
We were supposed to give the same "answers" as the previous build and the new framework was not supposed to affect it. But is sure did.
Man, did we scramble and get frustrated because there was a lot of legacy code that we had to sift through to figure out what it was really doing.
Thankfully, after most of the day, we figured out what the issues were and got it resolved, mostly. There is still some work that needs to get done but we should be all set for that by the end of the day, barring more problems.
Anyway, I now have a new pet peeve when it comes to code...commenting. There was little to no commenting in the code and the variable naming was atrocious. Naming variables is essentially free so name it appropriately like "totalCounts" or "isFound" or something at least descriptive. "x1" and "h" just don't cut it!
Very annoying but I found a way to get through it. Not that I get stressed out, but I picked up frustration waves from my co-worker and I did my best to deal with the crisis AND to try to keep the situation calm at the same time.
Ah well, that's my excuse for not writing yesterday, plus I babysat Mo after work so was a very full day, though no stress on the second part thankfully. :)
*aims laser pointer at legacy code authors and fires indiscriminately*
1 comment:
I am very anal about that stuff too. Also about writing.
I have been doing an online text proofreading thing sometimes that checks for errors in scanning of old books.
And I am not sure what AZ is playing at but he should not be snooping around the back end of porn movie sites any more. :)
Post a Comment