It's 1am here and I'm working my 88th workhour this month here... have bug that had to be solved tomorrow... but my mind not very clear for tracking why the numbers return by stored proc is wrong...
Very sleepy and miss my bed...
Loading User Information from Channel 9
Something went wrong getting user information from Channel 9
Loading User Information from MSDN
Something went wrong getting user information from MSDN
Loading Visual Studio Achievements
Something went wrong getting the Visual Studio Achievements
It's 1am here and I'm working my 88th workhour this month here... have bug that had to be solved tomorrow... but my mind not very clear for tracking why the numbers return by stored proc is wrong...
Very sleepy and miss my bed...
@cheong: It doesn't matter how important the bug is. A bug fixed on no sleep is two new bugs you don't know about yet.
@kettch: Indeed, at 3am I become a retard and the next day I don't even recognize my own code anymore.
I agree with the rest. Maybe it has to be solved by tomorrow, but you also have to not introduce two more bugs by tomorrow. It's a catch 22. The only thing you can do is limit the damage, and not fix the bug.
@kettch:Had to clear *that* bug before UAT. It's major function. If it's not fixed, the UAT would be a no-show.
Time to post a bounty on stackoverflow.com?
Have fixed the bug... "Premature optimization is the root of all evils."
I have always found it better to stop and sleep, then start again early the next morning; like everyone said, you cannot function without sleep, so just have the sleep first.
Herbie
11 hours ago, ZippyV wrote
@kettch: Indeed, at 3am I become a retard and the next day I don't even recognize my own code anymore.
I wish I could say that a good sleep makes my code better... but it's just as crap either way.
Add your 2¢