Well, there's a whole bunch of nothing out there this morning, but here's a few things that I thought might interest all of you - most of these are just general stories though:
First off, from the hard working folks over on Sitepoint, we have a new article about caching web pages. For those that are confused, Cache or Check? will help explain a few things. Essentially all a cache does is store copies of (or pointers to) previously accessed data. The main implementation in computer architecture is to use a small area of very fast memory (SRAM) to store copies of recently accessed information from your main memory (RAM) or hard drive, which are a lot slower. They give both sides of it in here, the good and the bad - why you should cache your web pages and why you shouldn't. For sites like ours where you want the latest and greatest, a cached version is just frustrating, but for people like Google, it's a godsend.

And, over on DevArticles.com this morning, they have an excerpt from the book Professional PHP Programming. The chapter that they cover is the "security" chapter - which is something that is quite often overlooked when people develop scripts (especially novice programmers). They just want to get it up and working, and don't think about the problems people could cause with a simple POST. In this article, they also talk about the server side too, making it a bit more secure than the standard-issue machine.

And, last but not least, from the Web Developer's Virtual Library, they have a new article about Usability Testing in Practice. This talks about how to get together a group of people, preferably ones as diverse as you can get, to take a crack at your website. It mentions how the "professionals" do it, and gives you a pretty good idea of what kind of things they watch out for. It's not going to tell you all of the tricks, obviously - but it does make one thing clear: If your site isn't something people can intuitively use and get around in, then you're dead in the water.