<?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: Web developers&#8217; areas of&#160;expertise</title>
	<atom:link href="http://akibjorklund.com/2009/areas-of-expertise/feed" rel="self" type="application/rss+xml" />
	<link>http://akibjorklund.com/2009/areas-of-expertise</link>
	<description>web generalist</description>
	<lastBuildDate>Thu, 09 Sep 2010 04:39:43 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Conscious Development &#187; Blog Archive &#187; Multi-competence required today</title>
		<link>http://akibjorklund.com/2009/areas-of-expertise#comment-14585</link>
		<dc:creator>Conscious Development &#187; Blog Archive &#187; Multi-competence required today</dc:creator>
		<pubDate>Tue, 29 Sep 2009 20:59:51 +0000</pubDate>
		<guid isPermaLink="false">http://akibjorklund.com/?p=1013#comment-14585</guid>
		<description>[...] My Colleaque Jouni had a nice post about what you need to learn in coming year if you are a Microsoft developer. Another colleaque, Aki, posted a nice summary of what expertise every web developer should possess. [...]</description>
		<content:encoded><![CDATA[<p>[...] My Colleaque Jouni had a nice post about what you need to learn in coming year if you are a Microsoft developer. Another colleaque, Aki, posted a nice summary of what expertise every web developer should possess. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aki Björklund</title>
		<link>http://akibjorklund.com/2009/areas-of-expertise#comment-13751</link>
		<dc:creator>Aki Björklund</dc:creator>
		<pubDate>Sun, 09 Aug 2009 11:14:27 +0000</pubDate>
		<guid isPermaLink="false">http://akibjorklund.com/?p=1013#comment-13751</guid>
		<description>Thank you for your insightful comment, I agree with you completely.

(I think I fixed your comment like you intended it to be, email me if you need other changes. I really should implement a preview.)</description>
		<content:encoded><![CDATA[<p>Thank you for your insightful comment, I agree with you completely.</p>
<p>(I think I fixed your comment like you intended it to be, email me if you need other changes. I really should implement a preview.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tuomas Salo</title>
		<link>http://akibjorklund.com/2009/areas-of-expertise#comment-13750</link>
		<dc:creator>Tuomas Salo</dc:creator>
		<pubDate>Sun, 09 Aug 2009 10:57:37 +0000</pubDate>
		<guid isPermaLink="false">http://akibjorklund.com/?p=1013#comment-13750</guid>
		<description>(Argh, I really hate these semi-HTML comment boxes without preview...)</description>
		<content:encoded><![CDATA[<p>(Argh, I really hate these semi-HTML comment boxes without preview&#8230;)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tuomas Salo</title>
		<link>http://akibjorklund.com/2009/areas-of-expertise#comment-13749</link>
		<dc:creator>Tuomas Salo</dc:creator>
		<pubDate>Sun, 09 Aug 2009 10:56:05 +0000</pubDate>
		<guid isPermaLink="false">http://akibjorklund.com/?p=1013#comment-13749</guid>
		<description>Security - I finally found it, just above the Misc category. I&#039;d prefer seeing security related items within most categories. It goes way beyond XSS and CSRF. Thinking securitywise is a lot more than just &quot;remembering to use htmlspecialchars()&quot;. There are new threats when using AJAX, JS libraries, etc.

As you said, the list is not complete. How about adding these:
 
&lt;em&gt;Validating your HTML/XML code&lt;/em&gt;. Especially, understanding the concepts of wellformedness vs. validity is important. And with XML, there should be an &lt;em&gt;How to really generate well-formed XML&lt;/em&gt; item, since people often fuck that up. I&#039;ve seen way too many unescaped ampersands in &quot;RSS feeds&quot; or other &quot;XML input&quot; that somebody generates with bad homegrown code.

You do mention performance, but only on the server side. Performance should be on the client side list, too. It has to do with browsers, AJAX, etc. Today we see a lot of &lt;code&gt;$(&#039;div&#039;).load(&quot;/anotherpage.php #just-a-small-part&quot;)&lt;/code&gt; crap, because people don&#039;t care or they really don&#039;t understand how the browser will do this trick.

Unicode/UTF-8/etc should be there, too. It&#039;s not too easy, and every developer &lt;em&gt;will&lt;/em&gt; face problems. Joel Spolsky has written &lt;a href=&quot;http://www.joelonsoftware.com/articles/Unicode.html&quot; rel=&quot;nofollow&quot;&gt;a good article on unicode&lt;/a&gt;. And yes, even character sets have to do with security.</description>
		<content:encoded><![CDATA[<p>Security &#8211; I finally found it, just above the Misc category. I&#8217;d prefer seeing security related items within most categories. It goes way beyond XSS and CSRF. Thinking securitywise is a lot more than just &#8220;remembering to use htmlspecialchars()&#8221;. There are new threats when using AJAX, JS libraries, etc.</p>
<p>As you said, the list is not complete. How about adding these:</p>
<p><em>Validating your HTML/XML code</em>. Especially, understanding the concepts of wellformedness vs. validity is important. And with XML, there should be an <em>How to really generate well-formed XML</em> item, since people often fuck that up. I&#8217;ve seen way too many unescaped ampersands in &#8220;RSS feeds&#8221; or other &#8220;XML input&#8221; that somebody generates with bad homegrown code.</p>
<p>You do mention performance, but only on the server side. Performance should be on the client side list, too. It has to do with browsers, AJAX, etc. Today we see a lot of <code>$('div').load("/anotherpage.php #just-a-small-part")</code> crap, because people don&#8217;t care or they really don&#8217;t understand how the browser will do this trick.</p>
<p>Unicode/UTF-8/etc should be there, too. It&#8217;s not too easy, and every developer <em>will</em> face problems. Joel Spolsky has written <a href="http://www.joelonsoftware.com/articles/Unicode.html">a good article on unicode</a>. And yes, even character sets have to do with security.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
