<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: 5 mistakes new web developers often make</title>
	<atom:link href="http://www.bradshawenterprises.com/blog/2008/5-mistakes-new-web-developers-often-make/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.bradshawenterprises.com/blog/2008/5-mistakes-new-web-developers-often-make/</link>
	<description>Richard Bradshaw&#039;s idea of what is interesting</description>
	<lastBuildDate>Sun, 20 Jun 2010 07:22:35 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: daleclara</title>
		<link>http://www.bradshawenterprises.com/blog/2008/5-mistakes-new-web-developers-often-make/comment-page-1/#comment-441</link>
		<dc:creator>daleclara</dc:creator>
		<pubDate>Fri, 09 Oct 2009 15:30:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.bradshawenterprises.com/blog/?p=51#comment-441</guid>
		<description>&lt;a href=&quot;http://sonicwebdesign.co.uk&quot; rel=&quot;nofollow&quot;&gt;&lt;b&gt;Web designers&lt;/b&gt;&lt;/a&gt;&lt;br&gt;&lt;br&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.</description>
		<content:encoded><![CDATA[<p><a href="http://sonicwebdesign.co.uk" rel="nofollow"><b>Web designers</b></a></p>
<p>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.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jack fisher</title>
		<link>http://www.bradshawenterprises.com/blog/2008/5-mistakes-new-web-developers-often-make/comment-page-1/#comment-269</link>
		<dc:creator>jack fisher</dc:creator>
		<pubDate>Mon, 12 Jan 2009 03:13:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.bradshawenterprises.com/blog/?p=51#comment-269</guid>
		<description>ya for sure these mistakes happen alot</description>
		<content:encoded><![CDATA[<p>ya for sure these mistakes happen alot</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: 5 errores habituales de desarrolladores web novatos &#124; BBPOWERDESIGN</title>
		<link>http://www.bradshawenterprises.com/blog/2008/5-mistakes-new-web-developers-often-make/comment-page-1/#comment-265</link>
		<dc:creator>5 errores habituales de desarrolladores web novatos &#124; BBPOWERDESIGN</dc:creator>
		<pubDate>Sat, 03 Jan 2009 13:48:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.bradshawenterprises.com/blog/?p=51#comment-265</guid>
		<description>[...] NOTA: Este artículo es una traducción (parcial) al español del original: 5 mistakes new web developers often make. [...]</description>
		<content:encoded><![CDATA[<p>[...] NOTA: Este artículo es una traducción (parcial) al español del original: 5 mistakes new web developers often make. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Carlos @ VPSmedia</title>
		<link>http://www.bradshawenterprises.com/blog/2008/5-mistakes-new-web-developers-often-make/comment-page-1/#comment-249</link>
		<dc:creator>Carlos @ VPSmedia</dc:creator>
		<pubDate>Fri, 24 Oct 2008 17:54:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.bradshawenterprises.com/blog/?p=51#comment-249</guid>
		<description>Make sure your server is well secured, here&#039;s one of our guides: &lt;a href=&quot;http://vpsmedia.com/articles/?p=25&quot;&gt;http://vpsmedia.com/articles/?p=25&lt;/a&gt;&lt;br&gt;its specific for Centos 5.2 but it should give anyone a pretty good idea.</description>
		<content:encoded><![CDATA[<p>Make sure your server is well secured, here&#39;s one of our guides: <a href="http://vpsmedia.com/articles/?p=25">http://vpsmedia.com/articles/?p=25</a><br />its specific for Centos 5.2 but it should give anyone a pretty good idea.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Webdesign Meppel</title>
		<link>http://www.bradshawenterprises.com/blog/2008/5-mistakes-new-web-developers-often-make/comment-page-1/#comment-220</link>
		<dc:creator>Webdesign Meppel</dc:creator>
		<pubDate>Thu, 25 Sep 2008 06:18:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.bradshawenterprises.com/blog/?p=51#comment-220</guid>
		<description>Mentioning some details about mysql_real_escape_string won&#039;t be a bad thing I guess...</description>
		<content:encoded><![CDATA[<p>Mentioning some details about mysql_real_escape_string won&#39;t be a bad thing I guess&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Poppo</title>
		<link>http://www.bradshawenterprises.com/blog/2008/5-mistakes-new-web-developers-often-make/comment-page-1/#comment-198</link>
		<dc:creator>Poppo</dc:creator>
		<pubDate>Thu, 28 Aug 2008 01:51:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.bradshawenterprises.com/blog/?p=51#comment-198</guid>
		<description>1 Mistake You Made:&lt;br&gt;&lt;br&gt;Don&#039;t make your section headers smaller and less bold than your section content.&lt;br&gt;&lt;br&gt;Why it&#039;s bad;&lt;br&gt;&lt;br&gt;Because it&#039;s very hard to skim your page for the start of the next section.</description>
		<content:encoded><![CDATA[<p>1 Mistake You Made:</p>
<p>Don&#39;t make your section headers smaller and less bold than your section content.</p>
<p>Why it&#39;s bad;</p>
<p>Because it&#39;s very hard to skim your page for the start of the next section.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pete White</title>
		<link>http://www.bradshawenterprises.com/blog/2008/5-mistakes-new-web-developers-often-make/comment-page-1/#comment-187</link>
		<dc:creator>Pete White</dc:creator>
		<pubDate>Tue, 22 Jul 2008 13:41:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.bradshawenterprises.com/blog/?p=51#comment-187</guid>
		<description>Good post, I will admit I&#039;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.</description>
		<content:encoded><![CDATA[<p>Good post, I will admit I&#8217;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.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: 5 erreurs que les nouveaux développeurs commetent souvent &#124; Le blog de David Loureiro</title>
		<link>http://www.bradshawenterprises.com/blog/2008/5-mistakes-new-web-developers-often-make/comment-page-1/#comment-137</link>
		<dc:creator>5 erreurs que les nouveaux développeurs commetent souvent &#124; Le blog de David Loureiro</dc:creator>
		<pubDate>Tue, 15 Jul 2008 12:34:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.bradshawenterprises.com/blog/?p=51#comment-137</guid>
		<description>[...] un article d&#233;crivant 5 d&#8217;entre elles et des moyens d&#8217;y rem&#233;dier :&#160;5 mistakes new web developers often make &#233;crit par Richard Bradshaw sur le site http://www.bradshawenterprises.com/blog/ [...]</description>
		<content:encoded><![CDATA[<p>[...] un article d&eacute;crivant 5 d&#8217;entre elles et des moyens d&#8217;y rem&eacute;dier :&nbsp;5 mistakes new web developers often make &eacute;crit par Richard Bradshaw sur le site <a href="http://www.bradshawenterprises.com/blog/" rel="nofollow">http://www.bradshawenterprises.com/blog/</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adam B</title>
		<link>http://www.bradshawenterprises.com/blog/2008/5-mistakes-new-web-developers-often-make/comment-page-1/#comment-167</link>
		<dc:creator>Adam B</dc:creator>
		<pubDate>Sun, 13 Jul 2008 01:17:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.bradshawenterprises.com/blog/?p=51#comment-167</guid>
		<description>Nice list. There are a few things I&#039;d recommend in addition primarily for security.  I&#039;ve dealt primarily with PHP, but this can be applied to other systems as well.&lt;br&gt;&lt;br&gt;On production, always disable error output.  Send your error messages to logs, but don&#039;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;br&gt;&lt;br&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&#039;s numeric only.  Make sure to run input through sanitizing like mysql_real_escape_string().  And if you&#039;re doing queries, make sure that your web user has ONLY the privileges it needs - don&#039;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;br&gt;&lt;br&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;br&gt;&lt;br&gt;Hope these tips help!</description>
		<content:encoded><![CDATA[<p>Nice list. There are a few things I&#8217;d recommend in addition primarily for security.  I&#8217;ve dealt primarily with PHP, but this can be applied to other systems as well.</p>
<p>On production, always disable error output.  Send your error messages to logs, but don&#8217;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.</p>
<p>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&#8217;s numeric only.  Make sure to run input through sanitizing like mysql_real_escape_string().  And if you&#8217;re doing queries, make sure that your web user has ONLY the privileges it needs &#8211; don&#8217;t give it drop table access or anything. If you want to go further, use two web users &#8211; 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.</p>
<p>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.</p>
<p>Hope these tips help!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Damien</title>
		<link>http://www.bradshawenterprises.com/blog/2008/5-mistakes-new-web-developers-often-make/comment-page-1/#comment-180</link>
		<dc:creator>Damien</dc:creator>
		<pubDate>Fri, 11 Jul 2008 12:30:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.bradshawenterprises.com/blog/?p=51#comment-180</guid>
		<description>reinventing the wheel shouldn&#039;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.</description>
		<content:encoded><![CDATA[<p>reinventing the wheel shouldn&#8217;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.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
