Haha 😂, actual code from 3rd party product we use:

  • 10
    Wow, just wow
  • 21
    Guaranteed random result all the time
  • 36
    When there's more things happening in the function declaration than in the function you know something is wrong
  • 8
    Care to name and shame?
  • 8
  • 3
    @2lazy2debug beat me to it,

    that function is usually found inside debug code, the part of code using this function should at least be surrounded by #if DEBUG

    so that when the code is compiled for production that doesn't get included and certificate validate remains untouched
  • 0
    @2lazy2debug it is just for safety, cuz under pressure sometimes warnings get slipped away and go unnoticed
  • 0
    @2lazy2debug hahaha good point XD
  • 0
    @nzeetee would be fun, but their security overall is so bad they don't event use Auth on the server part. so I would not want too many eyes on them before we switch provider.
  • 1
    @raldo94 rofl. I thought it was good conscience, then realised it was good business!
  • 2
    Less 😂, more of a 😱
  • 1
    And then, there are instances that these happen due to laziness of enclosing statements under a block and copy pasting

    More: www.gotofail.com
  • 1
    @gitlog ah, remember that one 😋
  • 0
    Sometimes you find something like that in methods that *should* be overridden in stuff like abstract classes, but in this case that's just wrong.
Add Comment