<?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 for Like Wow Online</title>
	<atom:link href="http://www.likewowonline.net/comments/feed" rel="self" type="application/rss+xml" />
	<link>http://www.likewowonline.net</link>
	<description>A weblog for designers, developers and anyone with an interest in web technology.</description>
	<lastBuildDate>Tue, 04 May 2010 18:53:49 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on Secrets to loving your corporate job by Graham Woods</title>
		<link>http://www.likewowonline.net/life/secrets-to-loving-your-corporate-job.html/comment-page-1#comment-251</link>
		<dc:creator>Graham Woods</dc:creator>
		<pubDate>Tue, 04 May 2010 18:53:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.likewowonline.net/?p=153#comment-251</guid>
		<description>This is great! Thank you for the gentle reminder, I love my job and the life I&#039;m creating..  Kudos Shimone, this is truly incitefull..</description>
		<content:encoded><![CDATA[<p>This is great! Thank you for the gentle reminder, I love my job and the life I&#8217;m creating..  Kudos Shimone, this is truly incitefull..</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Secrets to loving your corporate job by Natarajan</title>
		<link>http://www.likewowonline.net/life/secrets-to-loving-your-corporate-job.html/comment-page-1#comment-250</link>
		<dc:creator>Natarajan</dc:creator>
		<pubDate>Sat, 01 May 2010 08:14:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.likewowonline.net/?p=153#comment-250</guid>
		<description>Thanks Shimone. Good points there. I would like to share a few, learnt through experience.
 
1. Trust - this is one of the most often repeated keywords repeated in an organization, but it can be difficult at times. I believe this is the single most important factor that makes or breaks teamwork. It helps to remind oneself that &quot;Basically people are good&quot;. Only trust can grow further trust.
 
2. Situations are not people - Just because a situation sucks, doesn&#039;t mean that the people involved do. It is very easy and tempting to judge people based on their percieved stand on a particular issue or situation, but a mature person needs to remind himself that the person involved is not characterized by that particular situation. In many cases, people may represent their team policies or processes or something else that may be established, and it may need correction. That does not mean that the person is at fault - he or she is merely representing something else, and there is probably a lot more to that person than is apparent from any one situation.

3. Keep reviewing yourself - I found that sometimes it is very easy to fall into a negative and pessimistic attitude without realizing it. What works best for me is to keep asking myself, &quot;Will I hire someone who has this attitude?&quot;, &quot;Is this what the company is paying me for?&quot; and most of all, &quot;Is this what I am made of?&quot;. The important thing is to answer these questions honestly. It is a very fine line between pessimism and realism.
 
4. Be frank without being rude - I dont know about you, but I would rather have someone point out my mistakes to me with respect, than go and tell someone else about my mistakes. When you point out my mistake to my face, that says several things. One, that you trust that I have the intelligence to understand what you are saying. Two, that you trust my character and integrity to such an extent that you think I will make an honest judgment about myself and make corrections to myself if necessary.  Three, your real and genuine intention is to work with me, and not to put me down. When you trust me so much, of course I will trust you too.</description>
		<content:encoded><![CDATA[<p>Thanks Shimone. Good points there. I would like to share a few, learnt through experience.</p>
<p>1. Trust &#8211; this is one of the most often repeated keywords repeated in an organization, but it can be difficult at times. I believe this is the single most important factor that makes or breaks teamwork. It helps to remind oneself that &#8220;Basically people are good&#8221;. Only trust can grow further trust.</p>
<p>2. Situations are not people &#8211; Just because a situation sucks, doesn&#8217;t mean that the people involved do. It is very easy and tempting to judge people based on their percieved stand on a particular issue or situation, but a mature person needs to remind himself that the person involved is not characterized by that particular situation. In many cases, people may represent their team policies or processes or something else that may be established, and it may need correction. That does not mean that the person is at fault &#8211; he or she is merely representing something else, and there is probably a lot more to that person than is apparent from any one situation.</p>
<p>3. Keep reviewing yourself &#8211; I found that sometimes it is very easy to fall into a negative and pessimistic attitude without realizing it. What works best for me is to keep asking myself, &#8220;Will I hire someone who has this attitude?&#8221;, &#8220;Is this what the company is paying me for?&#8221; and most of all, &#8220;Is this what I am made of?&#8221;. The important thing is to answer these questions honestly. It is a very fine line between pessimism and realism.</p>
<p>4. Be frank without being rude &#8211; I dont know about you, but I would rather have someone point out my mistakes to me with respect, than go and tell someone else about my mistakes. When you point out my mistake to my face, that says several things. One, that you trust that I have the intelligence to understand what you are saying. Two, that you trust my character and integrity to such an extent that you think I will make an honest judgment about myself and make corrections to myself if necessary.  Three, your real and genuine intention is to work with me, and not to put me down. When you trust me so much, of course I will trust you too.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Secrets to loving your corporate job by Eema</title>
		<link>http://www.likewowonline.net/life/secrets-to-loving-your-corporate-job.html/comment-page-1#comment-249</link>
		<dc:creator>Eema</dc:creator>
		<pubDate>Fri, 30 Apr 2010 18:48:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.likewowonline.net/?p=153#comment-249</guid>
		<description>This is a brilliantly worded guide to a healthy, sustainable work ethic.</description>
		<content:encoded><![CDATA[<p>This is a brilliantly worded guide to a healthy, sustainable work ethic.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Secrets to loving your corporate job by Dakota Sullivan</title>
		<link>http://www.likewowonline.net/life/secrets-to-loving-your-corporate-job.html/comment-page-1#comment-247</link>
		<dc:creator>Dakota Sullivan</dc:creator>
		<pubDate>Fri, 30 Apr 2010 17:18:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.likewowonline.net/?p=153#comment-247</guid>
		<description>Right on! All smart, common sense stuff that are right under our noses and totally possible but most of us miss.</description>
		<content:encoded><![CDATA[<p>Right on! All smart, common sense stuff that are right under our noses and totally possible but most of us miss.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Secrets to loving your corporate job by Linda Bohnert</title>
		<link>http://www.likewowonline.net/life/secrets-to-loving-your-corporate-job.html/comment-page-1#comment-246</link>
		<dc:creator>Linda Bohnert</dc:creator>
		<pubDate>Fri, 30 Apr 2010 13:15:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.likewowonline.net/?p=153#comment-246</guid>
		<description>Fabulous!!   I love your insights.   It is amazing how simple it could be.</description>
		<content:encoded><![CDATA[<p>Fabulous!!   I love your insights.   It is amazing how simple it could be.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Accessible footnotes with HTML and CSS by Max Grabowski</title>
		<link>http://www.likewowonline.net/web/dev/accessible-footnotes.html/comment-page-1#comment-242</link>
		<dc:creator>Max Grabowski</dc:creator>
		<pubDate>Wed, 17 Mar 2010 20:30:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.likewowonline.net/presentation/accessible-footnotes.html#comment-242</guid>
		<description>Great article!  The only question that I have is:

What do you do when dealing with multiple superscripts to 1 footnote?  I see this on several sites that have legal disclosures.  You know, the 3 or 4 spots where you see the same asterisk (*).  Going from the astersks to the footnote seems easy, but not the trip back.

I can only think of a Javascript solution, where you would use the onClick event to pass the current superscript id to the &quot;back to content&quot; link&#039;s href value.</description>
		<content:encoded><![CDATA[<p>Great article!  The only question that I have is:</p>
<p>What do you do when dealing with multiple superscripts to 1 footnote?  I see this on several sites that have legal disclosures.  You know, the 3 or 4 spots where you see the same asterisk (*).  Going from the astersks to the footnote seems easy, but not the trip back.</p>
<p>I can only think of a Javascript solution, where you would use the onClick event to pass the current superscript id to the &#8220;back to content&#8221; link&#8217;s href value.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Accessible footnotes with HTML and CSS by Shimone Samuel</title>
		<link>http://www.likewowonline.net/web/dev/accessible-footnotes.html/comment-page-1#comment-179</link>
		<dc:creator>Shimone Samuel</dc:creator>
		<pubDate>Tue, 04 Aug 2009 17:55:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.likewowonline.net/presentation/accessible-footnotes.html#comment-179</guid>
		<description>Thanks for the feedback Matt. I did encounter that question when I created this and realized - what would I call the links? Aside from naming them differently there wouldn&#039;t be a practical way to name their &lt;em&gt;exact&lt;/em&gt; destination (e.g. &quot;return to sentence abc&quot;).

I suppose I could name the href or title cleverly but then automating the creation of footnotes with a CMS would be cumbersome.

Looking at the WCAG 2.0 website I see they use a similar convention for their in-page &#039;back&#039; links: &quot;Go to contents&quot; so I guess this remains the most practical method.

In this case, the &quot;return to article link&quot; returns you to the exact place you left off so clicking a footnote and returning should be seamless even if the title isn&#039;t unique.

Thanks!
Shimone</description>
		<content:encoded><![CDATA[<p>Thanks for the feedback Matt. I did encounter that question when I created this and realized &#8211; what would I call the links? Aside from naming them differently there wouldn&#8217;t be a practical way to name their <em>exact</em> destination (e.g. &#8220;return to sentence abc&#8221;).</p>
<p>I suppose I could name the href or title cleverly but then automating the creation of footnotes with a CMS would be cumbersome.</p>
<p>Looking at the WCAG 2.0 website I see they use a similar convention for their in-page &#8216;back&#8217; links: &#8220;Go to contents&#8221; so I guess this remains the most practical method.</p>
<p>In this case, the &#8220;return to article link&#8221; returns you to the exact place you left off so clicking a footnote and returning should be seamless even if the title isn&#8217;t unique.</p>
<p>Thanks!<br />
Shimone</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Accessible footnotes with HTML and CSS by Matt Williams</title>
		<link>http://www.likewowonline.net/web/dev/accessible-footnotes.html/comment-page-1#comment-178</link>
		<dc:creator>Matt Williams</dc:creator>
		<pubDate>Mon, 03 Aug 2009 12:01:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.likewowonline.net/presentation/accessible-footnotes.html#comment-178</guid>
		<description>I think having all of your &quot;return to article&quot; links saying the same thing might break an accessibility guideline.  They all link to different places but say the same thing.  How you would name them differently though would be tricky to work out.</description>
		<content:encoded><![CDATA[<p>I think having all of your &#8220;return to article&#8221; links saying the same thing might break an accessibility guideline.  They all link to different places but say the same thing.  How you would name them differently though would be tricky to work out.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Accessible footnotes with HTML and CSS by ekspekt</title>
		<link>http://www.likewowonline.net/web/dev/accessible-footnotes.html/comment-page-1#comment-176</link>
		<dc:creator>ekspekt</dc:creator>
		<pubDate>Tue, 30 Jun 2009 22:09:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.likewowonline.net/presentation/accessible-footnotes.html#comment-176</guid>
		<description>interesting post, will come back here, bookmarked your site</description>
		<content:encoded><![CDATA[<p>interesting post, will come back here, bookmarked your site</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Recommended reading from the 2009 Interaction and IA Summit conferences by JamesD</title>
		<link>http://www.likewowonline.net/web/ued/ixda-ia-recommendations.html/comment-page-1#comment-174</link>
		<dc:creator>JamesD</dc:creator>
		<pubDate>Thu, 11 Jun 2009 12:35:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.likewowonline.net/?p=58#comment-174</guid>
		<description>Thanks for the useful info. It&#039;s so interesting</description>
		<content:encoded><![CDATA[<p>Thanks for the useful info. It&#8217;s so interesting</p>
]]></content:encoded>
	</item>
</channel>
</rss>
