The SNL Jeopardy skits are the best
I love the Saturday Night Live skits that spoof Jeopardy. Will Ferrell is in classic form on every one. Here’s a site that has captured 13 of them for your pleasure. Have a look.
Archive for September, 2005
Cool new site to get great deals on eBay
I just came across this site that I think is a pretty cool concept. Not a very pretty site, but it has a lot of potential. The idea is to list auctions on eBay that have less than an hour left and the current bid is less than a dollar. Pretty cool. Check it out.
The president’s potty break plea
This is currently making the rounds big-time in the blogosphere. Evidently, the president has to ask permission to use the bathroom now. Somehow this leaves feeling a little squeemish when the most powerful man in the world is not a ‘take charge kind of guy’ enough to decide on his own that he can take a potty break.
Reuters Photog Captures Bush at U.N. With ‘Bathroom Break’ Note
How, when, and where to build data validation
During an application discussion with another developer today a question occured to me that I’m sure others have had. When and where do I start with my data validation in a web application?
Usually in a web application you have data validation in at least 2 places: the browser, and the server. The other developer I was working with felt that it was easier to code the validation using javascript in the browser, so he preferred to do it there first. I had to disagree with this. Looking at it from a couple of points of view, it seems more productive to code the validation first on the server-side.
From the project management, product delivery side of the house, it seems more important to have the validation happen on the server because at least when it’s there I can go ahead and deliver my application without fear of invalid data. If I code it first on the browser-side in javascript, then the user could always disable the javascript and still send me junk data.
From the ease of coding/testing side, it seems like a major hassle to test the server-side validation if I’ve already coded the browser-side validation. I have to somehow have a way of sending junk data to the server in order to test that the validation truly works, and that I am sending back valid messages to the end-user. If my front-end validation is already coded, this would generally mean disconnecting my functional validation javascript from my forms, or building a separate test harness for my server-side code. Either way, it means more work from a coding perspective.
So, I say build it on the server first. What do you think?