63
divanov
7y

9pm Project Manager: We have to push an update TONIGHT
9.45pm Devs: okay guys, all latest bugs are fixed, just needs final check and we can push the update
10:45pm Devs: Guys?...
11:45pm Guy in charge of testing: Uh doesn't work...
- What doesn't work?
- I dunno, I get an error message
- What's the (fucking) error message?!
Aaaaand silence
Fuck this I'm going to bed.

Comments
  • 42
    Omg why is this so hard for people to understand!?!?

    Client: Its not working
    Dev: What happened?
    Client: I don't know I got an error
    Dev: What was it?
    Client: I don't know I closed it out.
    Dev: Well what were you trying to when you got the error?
    Client: I don't remember
  • 2
    well maybe he/she was in the middle of nightly rituals.

    huehuehue
  • 1
    One possibility :
    1- create function to save text in a log file (for calling)
    Call it at the beginning of every function and in the end (start function xyz, end function xyz), that way you know what function is giving an error.
    If your code have exceptions you can also add custom error messages to the log.
  • 1
    @RodrigoF One better: a tagging log system with timestamps and indent levels.

    This way you can list info, warnings, errors, events, etc. and keep track of depth in a very easy-to-read format.
  • 1
    @Root way better... Well I'm just a noob and perfer your method
  • 0
    @CurseMeSlowly Bwahahaha
Add Comment