<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.1" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: Tipps for writing good performanced code in .NET</title>
	<link>http://bka-bonn.de/wordpress/index.php/2008/05/06/tips-for-writing-good-performanced-code-in-net/</link>
	<description>This is C++, we all have our segfaults.</description>
	<pubDate>Sun, 20 May 2012 12:11:47 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.1</generator>
		<item>
		<title>By: Tipps for writing good performanced code in .NET</title>
		<link>http://bka-bonn.de/wordpress/index.php/2008/05/06/tips-for-writing-good-performanced-code-in-net/#comment-59</link>
		<dc:creator>Tipps for writing good performanced code in .NET</dc:creator>
		<pubDate>Wed, 07 May 2008 01:59:33 +0000</pubDate>
		<guid>http://bka-bonn.de/wordpress/index.php/2008/05/06/tips-for-writing-good-performanced-code-in-net/#comment-59</guid>
		<description>[...] roulette tipps wrote an interesting post today onHere&#8217;s a quick excerptWriting code that runs quickly is sometimes at odds with writing code quickly. Writing unnecessary code is undoubtedly bad for work efficiency. However, itâs important to realize that different situations have different needs. &#8230; [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] roulette tipps wrote an interesting post today onHere&#8217;s a quick excerptWriting code that runs quickly is sometimes at odds with writing code quickly. Writing unnecessary code is undoubtedly bad for work efficiency. However, itâs important to realize that different situations have different needs. &#8230; [&#8230;]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

