http://disqus.com/people/d7ef68675d5d2b412c45a89646da905c/enSat, 12 Jul 2008 23:17:52 -0000http://bradshawenterprises.disqus.com/5_mistakes_new_web_developers_often_make_18/#comment-877884Nice list. There are a few things I'd recommend in addition primarily for security. I've dealt primarily with PHP, but this can be applied to other systems as well.<br><br>On production, always disable error output. Send your error messages to logs, but don't ever output them to the browser. Error messages, in addition to being unprofessional, can reveal details about your architecture that no one really needs to know.<br><br>Second, ALWAYS filter and validate input. Assume every user is trying to destroy your server. Go with a white-list approach. If an input is supposed to be a numeric ID, make sure it's numeric only. Make sure to run input through sanitizing like mysql_real_escape_string(). And if you're doing queries, make sure that your web user has ONLY the privileges it needs - don't give it drop table access or anything. If you want to go further, use two web users - one for read that only has select access, and the write, which has select, insert, update, and delete. Only use the write user when you actually need it.<br><br>Finally, when configuring your server, make the docroot as limited as possible. That is, stuff like include files and template files (if you have them) should not be accessible through the server.<br><br>Hope these tips help!Adam BSat, 12 Jul 2008 23:17:52 -0000http://antseyeview.disqus.com/customer_service_hell_t_mobile8230hot_spot_not/#comment-7128006I used to be in customer service. And it did suck a lot sometimes. But I dealt. For everyone saying "I'm in customer service, and the guy who wrote this is a douche": you're all self-pitying assholes who try to elevate your shitty position in the world by belittling customers who you're paid to help.<br><br>It's your job to help, and if you can't even get that right, well, no wonder you're still working as a CSA.Adam BWed, 20 Jun 2007 16:29:49 -0000