Aug 26, 2013 · Refactoring needs the safety harness of a unit test suite to remove that "Have I broken it?" feeling. Covering the bad code in a blanket of tests will help you whilst you strive for good clean …

If you haven't formally agreed upon code quality characteristics and a naming convention, then you can't rightly say that what they're doing is bad or wrong, but you could address it by calling it …

Oct 30, 2013 · The description of the 400 code is "the request could not be understood by the server due to malformed syntax " - so it shouldn't be used for validation errors, imho.

Here's a quote about magic number as a bad programming practice The term magic number also refers to the bad programming practice of using numbers directly in source code without explanation. In …

Feb 26, 2010 · What status code should I set for UPDATE (PUT) and DELETE (e.g. product successfully updated)?

I consider code that is littered with try / catch blocks to be a good target for code review and refactoring. It indicates that either exception handling is not well understood or the code has become an amœba …

400 Bad Request isn't bad but should generally be reserved for malformed syntax. OP seems to be more concerned about a case with well-formed syntax but invalid values. Plus 400 is a fairly common …

Oct 12, 2009 · Corey Haines, who proposed the subject, was convinced that if statement is absolute evil. His alternative was to create functions with predicates. Can you please explain to me why if is evil. I …

Jun 16, 2010 · The 400 Bad Request, as Gert suggested, remains a valid response code, but I think it is normally used to indicate lower-level problems. It could easily be interpreted as a malformed HTTP …

Apr 10, 2016 · I think what you are looking for is a do-while loop. I 100% agree that while (true) is not a good idea because it makes it hard to maintain this code and the way you are escaping the loop is …