|
DaWei... at this point I am ready to believe in anything. When you literally stand in front of a programmer who claims to have years of expierence in "C-Pound", you'll start to understand where I am coming from. No this, didn't happen to me, but I read about it on a forum once.
Although when I joined my school's website staff was about the time they started rewriting the entire site. Mostly because the administration wanted more content like videos and pictures to go along with our website as well as a new interface, so we decided to rewrite the whole thing. Well, just a few days ago I had to put up a "Snow Day" graphic on the old site, because our new one isn't completed yet. I've never worked with the old code before because I've never needed to, but it was HORRIBLE. It took me nearly an hour just to update that one graphic. Files that wern't even being used were left on the server. They were basically exact copies of the final version except for a few small changes so I basically made the graphics change in 3 different files before I found the one that was actually being used. Hundreds upon hundreds of lines of code were commented out and left that way in the final version. API files were scattered everywhere with no sense of organization and proper use of CSS?? HA! forget that, lets create 20 different CSS files with only one setting in each of them and only use them once. But guess what? Our old site still works like a charm.
Any GOOD programmer knows the security risks such as SQL-Injection and Buffer Overflows, but how many GOOD programmers are there??? Less than you would think and yes I too would label buffer overflows as a lesser known risk. This doesn't just apply to programmers either. Average users will make the dumbest of passwords all the time. They'll use their birthday or the name of their dog, or whatever.
Do a majority of people in general know about these risks? Yes they do. But exactly how large is a majority? Many times it swings as low as 60/40 and SQL-Injection fits in that category.
|