<?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"
	>
<channel>
	<title>Comments for r3T3k't</title>
	<atom:link href="http://tech.shirl.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://tech.shirl.com</link>
	<description>ranting and raving about (the sad state of) information technology</description>
	<pubDate>Thu, 20 Nov 2008 07:05:10 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>Comment on Code Tags in Blogs and Lack of Support Thereof by bshirley</title>
		<link>http://tech.shirl.com/2008/04/22/code-tags-in-blogs-and-lack-of-support-thereof/#comment-9</link>
		<dc:creator>bshirley</dc:creator>
		<pubDate>Mon, 28 Apr 2008 13:28:45 +0000</pubDate>
		<guid isPermaLink="false">http://tech.shirl.com/?p=34#comment-9</guid>
		<description>Hmm, this code is causing problems in Safari and FireFox 3.0b4.  In Safari, it's breaking on a blank line.  In FireFox it's ending at a blank line.

The pre tag works okay, though.</description>
		<content:encoded><![CDATA[<p>Hmm, this code is causing problems in Safari and FireFox 3.0b4.  In Safari, it&#8217;s breaking on a blank line.  In FireFox it&#8217;s ending at a blank line.</p>
<p>The pre tag works okay, though.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on You Have a Tech Job?  Learn to Write! by re-tech</title>
		<link>http://tech.shirl.com/2008/04/24/you-have-a-tech-job-learn-to-write/#comment-8</link>
		<dc:creator>re-tech</dc:creator>
		<pubDate>Thu, 24 Apr 2008 22:07:55 +0000</pubDate>
		<guid isPermaLink="false">http://tech.shirl.com/?p=35#comment-8</guid>
		<description>Thanks Harish,
 I'd much rather you put the content out there than not.  Let me assure you, I feel the pain of time being squeezed - and writing is not a quick or easy thing.  I've seen much worse examples, I just didn't want to take the time to go back and find them.

 You got unlucky enough to be in front of me when the weight of many things finally got to me.  And, yes, personal blogs should have the most leeway of all (after email, text messages, and any real-time messaging).  I hope you didn't take any of it personally, because I definitely didn't intend it that way!

As for press releases like that in the second half of my tirade, only lack of caring is an excuse.</description>
		<content:encoded><![CDATA[<p>Thanks Harish,<br />
 I&#8217;d much rather you put the content out there than not.  Let me assure you, I feel the pain of time being squeezed - and writing is not a quick or easy thing.  I&#8217;ve seen much worse examples, I just didn&#8217;t want to take the time to go back and find them.</p>
<p> You got unlucky enough to be in front of me when the weight of many things finally got to me.  And, yes, personal blogs should have the most leeway of all (after email, text messages, and any real-time messaging).  I hope you didn&#8217;t take any of it personally, because I definitely didn&#8217;t intend it that way!</p>
<p>As for press releases like that in the second half of my tirade, only lack of caring is an excuse.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on You Have a Tech Job?  Learn to Write! by Harish Sivaramakrishnan</title>
		<link>http://tech.shirl.com/2008/04/24/you-have-a-tech-job-learn-to-write/#comment-7</link>
		<dc:creator>Harish Sivaramakrishnan</dc:creator>
		<pubDate>Thu, 24 Apr 2008 17:49:09 +0000</pubDate>
		<guid isPermaLink="false">http://tech.shirl.com/?p=35#comment-7</guid>
		<description>Thanks for taking time to point out the errors in my blog - Some of the grammatical errors could have been totally avoided. I am going to get back to my post and make appropriate edits.

Having said that, I am quite convinced myself that I would never ever bother about capitalization or the occasional incorrect line spacing because a tech blog addresses a technical problem! Its not quite a literature piece that you take the English language more seriously than the actual subject matter itself. Personally, I would write a couple more articles in the time I would spend checking for cosmetic issues. That's the way I look at it. If the article is so inanely worded that one cannot make any sense out of it, then that's a whole different issue.

I would have agreed with you completely if I were writing a book. As far as personal blogs are concerned, I believe I have the creative freedom to write any which way, because it is my own personal space!

That's my thought! Once again, thanks a lot for visiting my blog.

Best Regards,
Harish</description>
		<content:encoded><![CDATA[<p>Thanks for taking time to point out the errors in my blog - Some of the grammatical errors could have been totally avoided. I am going to get back to my post and make appropriate edits.</p>
<p>Having said that, I am quite convinced myself that I would never ever bother about capitalization or the occasional incorrect line spacing because a tech blog addresses a technical problem! Its not quite a literature piece that you take the English language more seriously than the actual subject matter itself. Personally, I would write a couple more articles in the time I would spend checking for cosmetic issues. That&#8217;s the way I look at it. If the article is so inanely worded that one cannot make any sense out of it, then that&#8217;s a whole different issue.</p>
<p>I would have agreed with you completely if I were writing a book. As far as personal blogs are concerned, I believe I have the creative freedom to write any which way, because it is my own personal space!</p>
<p>That&#8217;s my thought! Once again, thanks a lot for visiting my blog.</p>
<p>Best Regards,<br />
Harish</p>
]]></content:encoded>
	</item>
</channel>
</rss>
