Coffeehouse Thread

9 posts

Still at work...

Back to Forum: Coffeehouse
  • User profile image
    cheong

    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...

    Recent Achievement unlocked: Code Avenger Tier 4/6: You see dead program. A lot!
    Last modified
  • User profile image
    kettch

    @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.

  • User profile image
    ZippyV

    @kettch: Indeed, at 3am I become a retard and the next day I don't even recognize my own code anymore.

  • User profile image
    Bas

    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.

  • User profile image
    cheong

    @kettch:Had to clear *that* bug before UAT. It's major function. If it's not fixed, the UAT would be a no-show.

    Recent Achievement unlocked: Code Avenger Tier 4/6: You see dead program. A lot!
    Last modified
  • User profile image
    JoshRoss

    Time to post a bounty on stackoverflow.com?

  • User profile image
    cheong

    Have fixed the bug... "Premature optimization is the root of all evils."

    Recent Achievement unlocked: Code Avenger Tier 4/6: You see dead program. A lot!
    Last modified
  • User profile image
    Dr Herbie

    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

  • User profile image
    elmer

    , 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.

Comments closed

Comments have been closed since this content was published more than 30 days ago, but if you'd like to continue the conversation, please create a new thread in our Forums, or Contact Us and let us know.