70

When you forget to remove your console.logs, and other developers be like:

Comments
  • 7
    Definitely better than forgetting your alerts! 😬
  • 5
    One of my biggest faux pas since joining the development world is leaving a log statement in a catch block which would occasionally print the word "bollocks" into the debug log.

    Speaking with colleagues of that company this error still exists in some live deployments.
  • 3
    Subrant: why the hell ever would the IE dev team decide to fatal error on a console.log when the browser inspector window is not open is beyond me. One errant console.log and BOOM, your site is a potato... There cannot be one good reason for this behavior, then again what am I saying I'm talking about IE 😆
  • 0
    @geewhiz actually it isn't an error thrown on purpose, I believe it is due to the fact that IE doesn't append the console module to the window when it isn't present. It is pretty damn annoying though.
  • 0
    That is the or good thing about IE. Since IE testing usually comes towards the end of the project, it alerts you about the consoles you left in!
  • 0
    @itsdaniel0 I guess that's an unexpected "feature" of IE haha
  • 0
    Other developers be like "use break points"
Add Comment