<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments for Software. Efficiency. Scalability.</title>
	<atom:link href="http://opletayev.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://opletayev.com</link>
	<description>Entia non sunt multiplicanda praeter necessitatem</description>
	<lastBuildDate>Tue, 09 Aug 2011 02:32:28 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>Comment on The Fallacy of Premature Optimization by The thing about TDD and pretty pictures » looseneurons.com</title>
		<link>http://opletayev.com/2010/09/08/the-fallacy-of-premature-optimization/#comment-72</link>
		<dc:creator><![CDATA[The thing about TDD and pretty pictures » looseneurons.com]]></dc:creator>
		<pubDate>Tue, 09 Aug 2011 02:32:28 +0000</pubDate>
		<guid isPermaLink="false">http://opletayev.com/?p=453#comment-72</guid>
		<description><![CDATA[[...] his post, &#8220;The Fallacy of Premature Optimization&#8221;, Mikhail Opletayev [...]]]></description>
		<content:encoded><![CDATA[<p>[...] his post, &#8220;The Fallacy of Premature Optimization&#8221;, Mikhail Opletayev [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The Fallacy of Premature Optimization by The thing about TDD and pretty pictures &#171; kenfaw.com</title>
		<link>http://opletayev.com/2010/09/08/the-fallacy-of-premature-optimization/#comment-67</link>
		<dc:creator><![CDATA[The thing about TDD and pretty pictures &#171; kenfaw.com]]></dc:creator>
		<pubDate>Sat, 25 Jun 2011 12:47:50 +0000</pubDate>
		<guid isPermaLink="false">http://opletayev.com/?p=453#comment-67</guid>
		<description><![CDATA[[...] his post, &#8220;The Fallacy of Premature Optimization&#8221;, Mikhail Opletayev [...]]]></description>
		<content:encoded><![CDATA[<p>[...] his post, &#8220;The Fallacy of Premature Optimization&#8221;, Mikhail Opletayev [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Understanding GC: allocating memory (part II) by Concurrency in new and existing programming languages &#171; Software. Efficiency. Scalability.</title>
		<link>http://opletayev.com/2010/01/11/understanding-gc-allocating-memory-part-ii/#comment-57</link>
		<dc:creator><![CDATA[Concurrency in new and existing programming languages &#171; Software. Efficiency. Scalability.]]></dc:creator>
		<pubDate>Tue, 07 Dec 2010 17:57:13 +0000</pubDate>
		<guid isPermaLink="false">http://opletayev.wordpress.com/?p=160#comment-57</guid>
		<description><![CDATA[[...] Memory management has arguably brought about the biggest productivity gain in the last 2 decades. Major imperative languages, such as Java and C# gained Garbage Collector (GC) and made developers stop about allocating memory. [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Memory management has arguably brought about the biggest productivity gain in the last 2 decades. Major imperative languages, such as Java and C# gained Garbage Collector (GC) and made developers stop about allocating memory. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Why people don&#8217;t switch from WinForms to WPF by Tune Up Your PC &#187; Post Topic &#187; 教えてください：Windows Forms 開発者が WPF / Silverlight に移行するには何がたいへんですか？</title>
		<link>http://opletayev.com/2010/11/18/why-people-dont-switch-from-winforms-to-wpf/#comment-48</link>
		<dc:creator><![CDATA[Tune Up Your PC &#187; Post Topic &#187; 教えてください：Windows Forms 開発者が WPF / Silverlight に移行するには何がたいへんですか？]]></dc:creator>
		<pubDate>Tue, 30 Nov 2010 09:10:55 +0000</pubDate>
		<guid isPermaLink="false">http://opletayev.com/?p=465#comment-48</guid>
		<description><![CDATA[[...] Why people don’t switch from WinForms to WPF [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Why people don’t switch from WinForms to WPF [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Technical Debt by Technical tax &#171; Software. Efficiency. Scalability.</title>
		<link>http://opletayev.com/2010/08/16/technical-debt/#comment-30</link>
		<dc:creator><![CDATA[Technical tax &#171; Software. Efficiency. Scalability.]]></dc:creator>
		<pubDate>Mon, 23 Aug 2010 19:58:07 +0000</pubDate>
		<guid isPermaLink="false">http://opletayev.com/?p=417#comment-30</guid>
		<description><![CDATA[[...] a comment &#187;  In the previous post, I talked about technical debt. It&#8217;s an essential part of any software project that has [...]]]></description>
		<content:encoded><![CDATA[<p>[...] a comment &raquo;  In the previous post, I talked about technical debt. It&#8217;s an essential part of any software project that has [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Windows 7 HDD Mirror Issue, SyncQueue TaskGroup by Windows 7 HDD Mirror Issue, SyncQueue TaskGroup (via Software. Efficiency. Scalability.) &#171; Chicago Mac/PC Support</title>
		<link>http://opletayev.com/2010/07/05/windows-7-hdd-mirror-issue-syncqueue-taskgroup/#comment-25</link>
		<dc:creator><![CDATA[Windows 7 HDD Mirror Issue, SyncQueue TaskGroup (via Software. Efficiency. Scalability.) &#171; Chicago Mac/PC Support]]></dc:creator>
		<pubDate>Mon, 05 Jul 2010 19:11:41 +0000</pubDate>
		<guid isPermaLink="false">http://opletayev.com/?p=404#comment-25</guid>
		<description><![CDATA[[...] I run Windows 7 on my workstation with SSD + RAID1 setup. The SSD contains Windows, Visual Studio, and some other tools that I use. The mirrored HDDs contain all data files and a backup copy of the SSD. This setup has been working fairly well for me because it gives an outstanding performance of the SSD drive (Windows 7 boots up in under 8 sec) and a stability of RAID1 which prevents any significant data loss. The only disappointing issue so far &#8230; Read More [...]]]></description>
		<content:encoded><![CDATA[<p>[...] I run Windows 7 on my workstation with SSD + RAID1 setup. The SSD contains Windows, Visual Studio, and some other tools that I use. The mirrored HDDs contain all data files and a backup copy of the SSD. This setup has been working fairly well for me because it gives an outstanding performance of the SSD drive (Windows 7 boots up in under 8 sec) and a stability of RAID1 which prevents any significant data loss. The only disappointing issue so far &#8230; Read More [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Interesting finds. Code to look at. by Yet another &#8220;Code to Look At&#8221; &#171; Software. Efficiency. Scalability.</title>
		<link>http://opletayev.com/2010/02/15/interesting-finds-code-to-look-at/#comment-17</link>
		<dc:creator><![CDATA[Yet another &#8220;Code to Look At&#8221; &#171; Software. Efficiency. Scalability.]]></dc:creator>
		<pubDate>Wed, 24 Feb 2010 21:56:43 +0000</pubDate>
		<guid isPermaLink="false">http://opletayev.wordpress.com/?p=284#comment-17</guid>
		<description><![CDATA[[...] 24, 2010   In the last post I mentioned some code samples from Interesting Finds by Jason Haley. Specifically, the Code to Look [...]]]></description>
		<content:encoded><![CDATA[<p>[...] 24, 2010   In the last post I mentioned some code samples from Interesting Finds by Jason Haley. Specifically, the Code to Look [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Google Buzz by Britt Somani</title>
		<link>http://opletayev.com/2010/02/11/google-buzz/#comment-16</link>
		<dc:creator><![CDATA[Britt Somani]]></dc:creator>
		<pubDate>Sun, 21 Feb 2010 23:30:42 +0000</pubDate>
		<guid isPermaLink="false">http://opletayev.wordpress.com/?p=275#comment-16</guid>
		<description><![CDATA[Personally I feel that Google Buzz&#039;s release was a little premature, especially the privacy concerns. I really think that Google&#039;s possibly going down the same path that Windows went through around the time of Windows 2K. The latest releases and releases appear to be less planned and I also feel like rushed in an attempt to be 1st to market, and or compete with its competitors releases. The privacy issue was an issue that did not require a computer science degree to figure out, a very basic review session would have identified these issues. Do you think Google may have received too much credit last year?]]></description>
		<content:encoded><![CDATA[<p>Personally I feel that Google Buzz&#8217;s release was a little premature, especially the privacy concerns. I really think that Google&#8217;s possibly going down the same path that Windows went through around the time of Windows 2K. The latest releases and releases appear to be less planned and I also feel like rushed in an attempt to be 1st to market, and or compete with its competitors releases. The privacy issue was an issue that did not require a computer science degree to figure out, a very basic review session would have identified these issues. Do you think Google may have received too much credit last year?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Understanding GC: Freeing memory (part I) by Understanding GC: allocating memory (part II) &#171; Software. Efficiency. Scalability.</title>
		<link>http://opletayev.com/2009/12/28/understanding-gc-freeing-memory-part-i/#comment-12</link>
		<dc:creator><![CDATA[Understanding GC: allocating memory (part II) &#171; Software. Efficiency. Scalability.]]></dc:creator>
		<pubDate>Mon, 11 Jan 2010 16:33:46 +0000</pubDate>
		<guid isPermaLink="false">http://opletayev.wordpress.com/?p=120#comment-12</guid>
		<description><![CDATA[[...] January 11, 2010   Previously:  Understanding GC: freeing memory (Part I) [...]]]></description>
		<content:encoded><![CDATA[<p>[...] January 11, 2010   Previously:  Understanding GC: freeing memory (Part I) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Google Talk memory leak by Understanding GC: Freeing memory (part I) &#171; Software. Efficiency. Scalability.</title>
		<link>http://opletayev.com/2009/12/16/google-talk-memory-leak/#comment-6</link>
		<dc:creator><![CDATA[Understanding GC: Freeing memory (part I) &#171; Software. Efficiency. Scalability.]]></dc:creator>
		<pubDate>Mon, 28 Dec 2009 20:12:14 +0000</pubDate>
		<guid isPermaLink="false">http://opletayev.wordpress.com/?p=114#comment-6</guid>
		<description><![CDATA[[...] leaks. It was a huge problem then and it is still a problem now. Even companies like Google can&#8217;t keep their products without leaks. GC has made it a lot [...]]]></description>
		<content:encoded><![CDATA[<p>[...] leaks. It was a huge problem then and it is still a problem now. Even companies like Google can&#8217;t keep their products without leaks. GC has made it a lot [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

