3 ms·

Wow. There were pull requests that were accepted to this project: https://github.com/Mikkeren/FizzBuzzEnterpriseEdition/pulls?direction=desc&page=1&sort=create

• SatvikBeri 14y ago
  My favorite: Change <= to < and == "One-liners lead to unclear code that has too much responsibility crammed into too little space. It's better to do less per line and keep the code readable. This changes the very complex and ambiguous operation <= into two separate, easily understood operations < and ==."
  • kibwen 14y ago
    Last week my colleagues and I realized that the official, Zend-provided, XML-based communication system that allows our PHP middle-end to talk to our RPG-based backend doesn't allow you to return any character string that includes a less-than symbol. One of our routines returns a SQL string. Sometimes SQL strings contain less-than symbols. After much handwringing and an official bugfix that fixed nothing whatsoever, we decided on the next-best solution: all instances of `where foo < bar` must be generated as `where foo != bar and foo !> bar`. I shit you not, that is a not-greater-than operator. http://pic.dhe.ibm.com/infocenter/dzichelp/v2r2/index.jsp?topic=%2Fcom.ibm.qmf.doc.ref%2Fdsqi2mst263.htm http://pic.dhe.ibm.com/infocenter/dzichelp/v2r2/index.jsp?to... I may sound frustrated, but I'm not. We all had a good laugh at the workaround and got back to work. This sort of thing is sometimes known as "job security".
    • sbmassey 14y ago
      why not just use 'where bar > foo'?
      • kibwen 14y ago
        Ugh, I really don't feel like explaining. :P Long story short: bureaucracy.