Forums
Kevin S. works on websites for a living.
Well, actually, "work" might not be an adequate description considering that part of Kevin's job requires that he is half clarvoyant and half mountain sherpa when it comes to digging through the several huge codebases globbed together abominations of open source, third-party components that he is expected to support.
"Some time ago I was checking the business logic that a friend had done for a system." writes Brian, "While I was debugging, I found this awesome piece of code. I understand that application logic should be bulletproofed to handle any kind of data condition passed to it, nulls, double and single quotes, etc., but I felt this to be an example of over-engineering a solution."
Jun 10
public boolean isBooleanFalse(boolean value) {
boolean response = false;
if (value == true) {
response = false;
} else {
response = true;
}
return response;
}
Working as a DBA in academia, Paul received a notice that a certain newly migrated user schema, specifically the one used by the enrollment tracking system, had swelled to 281 tables and was growing. This had struck Paul as being very strange since the tracking system wasn't all that complicated.
When a student is registering for a class, and want to know if there's room left, they need two pieces of information - the Course ID and the Semester Number.