Thanks to PHPComplete.com for a link to an interesting artile on Optimizing PHP this morning. This is a huge piece with tons of good ideas on how you can get your code as lean and sleek as possible - including tons of examples and "how not to do it" examples as well. If you're interested in that little extra edge you get from one way of doing things versus another, then this article is for you. There really is tons here....

One thing that too many people forget about when they write their apps is something that could cause the most damage later on down the road - SQL Injections. For those unsure what these "injections" are, SQL injections are: when an attacker "injects" or manipulates SQL code. By adding unexpected SQL to a query, it is possible to manipulate a database in ways initially unthought of by the database administrator/developer. There's some good examples here - and some stuff that should probably scare a lot of people out there (including me). Thankfully, they do provide some preventative measures and ideas that will help you keep your data safe from prying eyes.

And, lastly, there's a piece over on Builder.com that talks about Security through obscurity and how it is *not* a good idea (at all). Too many times, it's just too easy to post a script up and just not tell anyone about it. More often than not, though, this will bite you in the hindquarters later on, especially if some bored little kid gets a hold of it (not that I've had expereince or anything). The article just gives some basic "dos and don'ts" to those out there who think that just because people can't find it, means it's safe....