<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Interesting Things - Latest Comments in 5 mistakes new web developers often make</title><link>http://bradshawenterprises.disqus.com/</link><description></description><atom:link href="https://bradshawenterprises.disqus.com/5_mistakes_new_web_developers_often_make_18/latest.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Thu, 22 Sep 2011 01:15:26 -0000</lastBuildDate><item><title>Re: 5 mistakes new web developers often make</title><link>http://www.bradshawenterprises.com/blog/2008/5-mistakes-new-web-developers-often-make/#comment-317201225</link><description>&lt;p&gt;Nice list really interesting &lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mauritius web Design</dc:creator><pubDate>Thu, 22 Sep 2011 01:15:26 -0000</pubDate></item><item><title>Re: 5 mistakes new web developers often make</title><link>http://www.bradshawenterprises.com/blog/2008/5-mistakes-new-web-developers-often-make/#comment-19654024</link><description>&lt;p&gt;&lt;a href="http://sonicwebdesign.co.uk" rel="nofollow noopener" target="_blank" title="http://sonicwebdesign.co.uk"&gt;&lt;b&gt;Web designers&lt;/b&gt;&lt;/a&gt;&lt;/p&gt;&lt;p&gt;If you have decided that you need a good website for your business,the next step is to decide who should create it.This decision is one that needs a lot of attention because if on the one hand, a well-organized and attractive web design can help you tremendously in making more money; on the other hand,a poorly designed website can cost you money, drive away customers, and can hurt your company reputation.&lt;br&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">PS3 Controllers </dc:creator><pubDate>Fri, 09 Oct 2009 05:30:03 -0000</pubDate></item><item><title>Re: 5 mistakes new web developers often make</title><link>http://www.bradshawenterprises.com/blog/2008/5-mistakes-new-web-developers-often-make/#comment-19483882</link><description>&lt;p&gt;I have not much time, but I've got many useful things here, love it!&lt;br&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">antibacterial_hand_sanitizers</dc:creator><pubDate>Thu, 08 Oct 2009 03:25:45 -0000</pubDate></item><item><title>Re: 5 mistakes new web developers often make</title><link>http://www.bradshawenterprises.com/blog/2008/5-mistakes-new-web-developers-often-make/#comment-5068902</link><description>&lt;p&gt;ya for sure these mistakes happen alot&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">jack fisher</dc:creator><pubDate>Mon, 12 Jan 2009 01:13:30 -0000</pubDate></item><item><title>Re: 5 mistakes new web developers often make</title><link>http://www.bradshawenterprises.com/blog/2008/5-mistakes-new-web-developers-often-make/#comment-3281090</link><description>&lt;p&gt;Make sure your server is well secured, here's one of our guides: &lt;a href="http://vpsmedia.com/articles/?p=25" rel="nofollow noopener" target="_blank" title="http://vpsmedia.com/articles/?p=25"&gt;http://vpsmedia.com/article...&lt;/a&gt;&lt;br&gt;its specific for Centos 5.2 but it should give anyone a pretty good idea.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Carlos @ VPSmedia</dc:creator><pubDate>Fri, 24 Oct 2008 15:54:37 -0000</pubDate></item><item><title>Re: 5 mistakes new web developers often make</title><link>http://www.bradshawenterprises.com/blog/2008/5-mistakes-new-web-developers-often-make/#comment-2622632</link><description>&lt;p&gt;Mentioning some details about mysql_real_escape_string won't be a bad thing I guess...&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Webdesign Meppel</dc:creator><pubDate>Thu, 25 Sep 2008 04:18:38 -0000</pubDate></item><item><title>Re: 5 mistakes new web developers often make</title><link>http://www.bradshawenterprises.com/blog/2008/5-mistakes-new-web-developers-often-make/#comment-1889079</link><description>&lt;p&gt;1 Mistake You Made:&lt;/p&gt;&lt;p&gt;Don't make your section headers smaller and less bold than your section content.&lt;/p&gt;&lt;p&gt;Why it's bad;&lt;/p&gt;&lt;p&gt;Because it's very hard to skim your page for the start of the next section.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Poppo</dc:creator><pubDate>Wed, 27 Aug 2008 23:51:58 -0000</pubDate></item><item><title>Re: 5 mistakes new web developers often make</title><link>http://www.bradshawenterprises.com/blog/2008/5-mistakes-new-web-developers-often-make/#comment-966760</link><description>&lt;p&gt;Good post, I will admit I've done a couple of them before. Fortunately I use Drupal now and it comes with Jquery which has a lot of the Javascript I need built in.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Pete White</dc:creator><pubDate>Tue, 22 Jul 2008 11:41:36 -0000</pubDate></item><item><title>Re: 5 mistakes new web developers often make</title><link>http://www.bradshawenterprises.com/blog/2008/5-mistakes-new-web-developers-often-make/#comment-877884</link><description>&lt;p&gt;Nice 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.&lt;/p&gt;&lt;p&gt;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.&lt;/p&gt;&lt;p&gt;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.&lt;/p&gt;&lt;p&gt;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.&lt;/p&gt;&lt;p&gt;Hope these tips help!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Adam B</dc:creator><pubDate>Sat, 12 Jul 2008 23:17:52 -0000</pubDate></item><item><title>Re: 5 mistakes new web developers often make</title><link>http://www.bradshawenterprises.com/blog/2008/5-mistakes-new-web-developers-often-make/#comment-864533</link><description>&lt;p&gt;reinventing the wheel shouldn't be a problem for a company specializing in wheel development.  why should bob smith try to make the next GoodYear tire clone out of play dough and an etch-a-sketch. &lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Damien</dc:creator><pubDate>Fri, 11 Jul 2008 10:30:57 -0000</pubDate></item><item><title>Re: 5 mistakes new web developers often make</title><link>http://www.bradshawenterprises.com/blog/2008/5-mistakes-new-web-developers-often-make/#comment-831328</link><description>&lt;p&gt;#6. Don't forget to spell check before posting your article *nudge nudge*&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">imgriff</dc:creator><pubDate>Mon, 07 Jul 2008 19:29:35 -0000</pubDate></item><item><title>Re: 5 mistakes new web developers often make</title><link>http://www.bradshawenterprises.com/blog/2008/5-mistakes-new-web-developers-often-make/#comment-818786</link><description>&lt;p&gt;Good point with number 5. These javascript/ajax frameworks have been thoroughly tested in multiple browsers.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">stuffigoogled</dc:creator><pubDate>Sat, 05 Jul 2008 13:40:46 -0000</pubDate></item><item><title>Re: 5 mistakes new web developers often make</title><link>http://www.bradshawenterprises.com/blog/2008/5-mistakes-new-web-developers-often-make/#comment-818412</link><description>&lt;p&gt;#5 - so true&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Vince</dc:creator><pubDate>Sat, 05 Jul 2008 12:08:50 -0000</pubDate></item><item><title>Re: 5 mistakes new web developers often make</title><link>http://www.bradshawenterprises.com/blog/2008/5-mistakes-new-web-developers-often-make/#comment-817705</link><description>&lt;p&gt;I think it is acceptable to reinvent another model of the wheel&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Sarmad</dc:creator><pubDate>Sat, 05 Jul 2008 09:03:10 -0000</pubDate></item><item><title>Re: 5 mistakes new web developers often make</title><link>http://www.bradshawenterprises.com/blog/2008/5-mistakes-new-web-developers-often-make/#comment-815578</link><description>&lt;p&gt;Thanks for the article!&lt;/p&gt;&lt;p&gt;A point though about naming of include files - the best solution is to place them in a directory that's not directly accessible to the web. Your PHP scripts will still be able to include them just fine.&lt;/p&gt;&lt;p&gt;If you do have to have them in a web-accessible directory for some reason, at least place them in a directory all of their own. Then place a htaccess file in there containing the following:&lt;/p&gt;&lt;p&gt;&amp;lt;files *=""&amp;gt;&lt;/p&gt;&lt;p&gt;order allow,deny&lt;/p&gt;&lt;p&gt;deny from all&lt;/p&gt;&lt;p&gt;&amp;lt;/files&amp;gt;&lt;/p&gt;&lt;p&gt;It's a mistake to think that giving your includes .php extensions makes them entirely safe. Should anyone ever try to access them individually (which is fairly unlikely anyway) they might not see your raw PHP code, but that code would be executed, with unknown consequences.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Kukas</dc:creator><pubDate>Fri, 04 Jul 2008 17:10:28 -0000</pubDate></item><item><title>Re: 5 mistakes new web developers often make</title><link>http://www.bradshawenterprises.com/blog/2008/5-mistakes-new-web-developers-often-make/#comment-815160</link><description>&lt;p&gt;A thing I learned;&lt;br&gt;Use many functions instead of copy and paste, and use stlye classes instead of coyping single style attributes^^&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">ktb</dc:creator><pubDate>Fri, 04 Jul 2008 15:27:41 -0000</pubDate></item><item><title>Re: 5 mistakes new web developers often make</title><link>http://www.bradshawenterprises.com/blog/2008/5-mistakes-new-web-developers-often-make/#comment-789977</link><description>&lt;p&gt;Thanks!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Richard Bradshaw</dc:creator><pubDate>Tue, 01 Jul 2008 11:50:59 -0000</pubDate></item><item><title>Re: 5 mistakes new web developers often make</title><link>http://www.bradshawenterprises.com/blog/2008/5-mistakes-new-web-developers-often-make/#comment-788243</link><description>&lt;p&gt;nice useful article.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">paresh</dc:creator><pubDate>Tue, 01 Jul 2008 07:53:20 -0000</pubDate></item><item><title>Re: 5 mistakes new web developers often make</title><link>http://www.bradshawenterprises.com/blog/2008/5-mistakes-new-web-developers-often-make/#comment-788060</link><description>&lt;p&gt;If  Wheels were never reinvented&lt;br&gt;we would be still using the tyre of rock&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Vinod Pahuja</dc:creator><pubDate>Tue, 01 Jul 2008 06:54:23 -0000</pubDate></item><item><title>Re: 5 mistakes new web developers often make</title><link>http://www.bradshawenterprises.com/blog/2008/5-mistakes-new-web-developers-often-make/#comment-786306</link><description>&lt;p&gt;Also, avoid learning grammar from the internet.&lt;/p&gt;&lt;p&gt;You do have a point, however poorly written it may be. :p&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">testerman5</dc:creator><pubDate>Mon, 30 Jun 2008 21:49:32 -0000</pubDate></item><item><title>Re: 5 mistakes new web developers often make</title><link>http://www.bradshawenterprises.com/blog/2008/5-mistakes-new-web-developers-often-make/#comment-784555</link><description>&lt;p&gt;Wow.  This is all excellent advice, even for us pros (who all too often forget the basics).  On "Don't reinvent the wheel," it's worth mentioning that learning about pre-existing platforms is a marketable job skill in and of itself.  For example, I learned WordPress because I like to blog.  However, because I developed that expertise, I now do a lot of lucrative side work setting up, customizing, and debugging WordPress installations.  Learning existing tools can be well worth it from more than an efficiency standpoint.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Stephen Ward</dc:creator><pubDate>Mon, 30 Jun 2008 17:01:41 -0000</pubDate></item><item><title>Re: 5 mistakes new web developers often make</title><link>http://www.bradshawenterprises.com/blog/2008/5-mistakes-new-web-developers-often-make/#comment-783350</link><description>&lt;p&gt;I learned #2 the hard way. Built a site for a local dancing club in the beginning of my career, and didn't bother to worry about security.&lt;/p&gt;&lt;p&gt;2 months later I get a call, that their guestbook was full of spam, and that it had broken completely recently (a meta redirect inserted in the comment).&lt;/p&gt;&lt;p&gt;I quickly added a captcha and made sure no SQL or Javascript injection was possible etc. This is a given today, no matter how small the project.&lt;/p&gt;&lt;p&gt;Good read.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">D</dc:creator><pubDate>Mon, 30 Jun 2008 14:41:37 -0000</pubDate></item><item><title>Re: 5 mistakes new web developers often make</title><link>http://www.bradshawenterprises.com/blog/2008/5-mistakes-new-web-developers-often-make/#comment-782347</link><description>&lt;p&gt;Edited to fix that... good thinking!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Richard Bradshaw</dc:creator><pubDate>Mon, 30 Jun 2008 12:40:50 -0000</pubDate></item><item><title>Re: 5 mistakes new web developers often make</title><link>http://www.bradshawenterprises.com/blog/2008/5-mistakes-new-web-developers-often-make/#comment-782124</link><description>&lt;p&gt;Shouldn't that be "Don't ignore semantic design"?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Elaine</dc:creator><pubDate>Mon, 30 Jun 2008 12:16:08 -0000</pubDate></item><item><title>Re: 5 mistakes new web developers often make</title><link>http://www.bradshawenterprises.com/blog/2008/5-mistakes-new-web-developers-often-make/#comment-774296</link><description>&lt;p&gt;Good work,  But in my case, the above issues doesn't cause more problem to the website except point no 1.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">A Suresh Kumar</dc:creator><pubDate>Sun, 29 Jun 2008 12:40:52 -0000</pubDate></item></channel></rss>