49

confused screaming!!

Comments
  • 2
    ohhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhh god
  • 5
    I love that it's backwards, too.

    That dev needs to be murdered.
  • 5
    So much verbosity to yield a wrong result

    At least he didn't use an if else in the first function/method
  • 0
    Let me pay your drink. That lad sure did a big one.
  • 1
    Repost. But the still funny.
  • 1
    I remember when DevExpress introduced their own implementation of Boolean, so there CAN be a reason - IIRC it included an additonal state of undefined (which was hardly ever neccessary).

    Failing that ... yeah.

    I just did a code review this morning where an old function of mine which did all there was to do in like 10 lines of code got separated into three layers of functions scattered over the class. I guess that's how you do it these days, single responsibility and all, but personally, I'll take "see everything that happens at a glance" over "clean single responsibility structure" any day. Until the code gets considerably longer or is reused/reuseable elsewhere, that is.
  • 3
    git commit die --force
Add Comment