<?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 on: Call yourself a Web Professional</title>
	<atom:link href="http://www.wiredvision.com/2005/11/16/call-yourself-a-web-professional/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.wiredvision.com/2005/11/16/call-yourself-a-web-professional/</link>
	<description>Home to Keith McLaughlin, a web developer from Dublin, Ireland.</description>
	<pubDate>Thu, 20 Nov 2008 13:33:36 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.1</generator>
		<item>
		<title>By: nortypig</title>
		<link>http://www.wiredvision.com/2005/11/16/call-yourself-a-web-professional/#comment-236</link>
		<dc:creator>nortypig</dc:creator>
		<pubDate>Tue, 10 Jan 2006 21:14:25 +0000</pubDate>
		<guid isPermaLink="false">http://70.47.103.12/~wired/?p=90#comment-236</guid>
		<description>A sensible enough post and quite true. I do have concerns that professional in the context of doctor or lawyer is an earned thing but professional in the context we're talking is a self-proclaimed thing. That can be dangerous. Professionalism goes beyond the code to quality of service, ethical issues and much more. If you know what I mean. I understand the context of the statement 'the new professional' but think it may be the wrong words for a right thing.

While I'm probably someone who would be considered elitist as a moderately unknown standardista I hope I try to remain balanced. If I don't feel free to come over and harangue me. I don't want an exclusive Web where anyone can't get online easily and with soup. That's different. But I'd like to see commercial sites go up a notch and adopt some of these better practices.

I actually took some umbrage to Oxton's line there as well, coincidentally lol. No I don't want that Web for sure. Although I agree I'd like to see better practices for web dev firms out there currently producing junk code. I guess.</description>
		<content:encoded><![CDATA[<p>A sensible enough post and quite true. I do have concerns that professional in the context of doctor or lawyer is an earned thing but professional in the context we&#8217;re talking is a self-proclaimed thing. That can be dangerous. Professionalism goes beyond the code to quality of service, ethical issues and much more. If you know what I mean. I understand the context of the statement &#8216;the new professional&#8217; but think it may be the wrong words for a right thing.</p>
<p>While I&#8217;m probably someone who would be considered elitist as a moderately unknown standardista I hope I try to remain balanced. If I don&#8217;t feel free to come over and harangue me. I don&#8217;t want an exclusive Web where anyone can&#8217;t get online easily and with soup. That&#8217;s different. But I&#8217;d like to see commercial sites go up a notch and adopt some of these better practices.</p>
<p>I actually took some umbrage to Oxton&#8217;s line there as well, coincidentally lol. No I don&#8217;t want that Web for sure. Although I agree I&#8217;d like to see better practices for web dev firms out there currently producing junk code. I guess.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: write.myobie.com &#187; Blog Archive &#187; Chinese Food or Web Professional?</title>
		<link>http://www.wiredvision.com/2005/11/16/call-yourself-a-web-professional/#comment-235</link>
		<dc:creator>write.myobie.com &#187; Blog Archive &#187; Chinese Food or Web Professional?</dc:creator>
		<pubDate>Mon, 05 Dec 2005 02:49:35 +0000</pubDate>
		<guid isPermaLink="false">http://70.47.103.12/~wired/?p=90#comment-235</guid>
		<description>[...] Recently John Oxton has been slammed for very colorfully explaining that those who wish to call themselves web professionals should at least learn HTML. He states: [...]</description>
		<content:encoded><![CDATA[<p>[...] Recently John Oxton has been slammed for very colorfully explaining that those who wish to call themselves web professionals should at least learn HTML. He states: [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jake</title>
		<link>http://www.wiredvision.com/2005/11/16/call-yourself-a-web-professional/#comment-234</link>
		<dc:creator>Jake</dc:creator>
		<pubDate>Wed, 23 Nov 2005 23:39:20 +0000</pubDate>
		<guid isPermaLink="false">http://70.47.103.12/~wired/?p=90#comment-234</guid>
		<description>I always thought the definition of a 'professional' is somebody who receives an income from their chosen field, as opposed to an 'amateur' who does not.

Theoretically, skill or quality actually plays no role in determining whether someone is an amateur or a professional.

There are good and bad in both camps.
Sad but true.</description>
		<content:encoded><![CDATA[<p>I always thought the definition of a &#8216;professional&#8217; is somebody who receives an income from their chosen field, as opposed to an &#8216;amateur&#8217; who does not.</p>
<p>Theoretically, skill or quality actually plays no role in determining whether someone is an amateur or a professional.</p>
<p>There are good and bad in both camps.<br />
Sad but true.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: &#187; John Oxton Ripped : Pig Work : Weblog of Freelance Designer Steven Clark aka Norty Pig, Hobart, Tasmania</title>
		<link>http://www.wiredvision.com/2005/11/16/call-yourself-a-web-professional/#comment-233</link>
		<dc:creator>&#187; John Oxton Ripped : Pig Work : Weblog of Freelance Designer Steven Clark aka Norty Pig, Hobart, Tasmania</dc:creator>
		<pubDate>Fri, 18 Nov 2005 23:49:04 +0000</pubDate>
		<guid isPermaLink="false">http://70.47.103.12/~wired/?p=90#comment-233</guid>
		<description>[...] I did agree with one anti-John Oxton statement from wiredvision regarding the web professional conversation of late. But I&#8217;ll hand this to the guy I only found this link because John himself pointed to it from JoshuaInk. So kudos for that one dude.    Top [...]</description>
		<content:encoded><![CDATA[<p>[...] I did agree with one anti-John Oxton statement from wiredvision regarding the web professional conversation of late. But I&#8217;ll hand this to the guy I only found this link because John himself pointed to it from JoshuaInk. So kudos for that one dude.    Top [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Patrick</title>
		<link>http://www.wiredvision.com/2005/11/16/call-yourself-a-web-professional/#comment-232</link>
		<dc:creator>Patrick</dc:creator>
		<pubDate>Thu, 17 Nov 2005 15:56:21 +0000</pubDate>
		<guid isPermaLink="false">http://70.47.103.12/~wired/?p=90#comment-232</guid>
		<description>I'm not a web professional.

Oh well.</description>
		<content:encoded><![CDATA[<p>I&#8217;m not a web professional.</p>
<p>Oh well.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stefan</title>
		<link>http://www.wiredvision.com/2005/11/16/call-yourself-a-web-professional/#comment-231</link>
		<dc:creator>Stefan</dc:creator>
		<pubDate>Thu, 17 Nov 2005 09:29:24 +0000</pubDate>
		<guid isPermaLink="false">http://70.47.103.12/~wired/?p=90#comment-231</guid>
		<description>The problem with &lt;acronym title="Hypertext Markup Language"&gt;HTML&lt;/acronym&gt; is, a whole bunch of wannabe-professionals with Frontpage 2003 earn their money, destroy the prices, quality and the idea behind the net. HTML is no secret, everyone may learn to code with accurate syntax - but they just don't care.

&lt;blockquote&gt;"What does this mean, there is no &#60;comment&#62;-tag? How do you do comments in html…&lt;/blockquote&gt;

And &lt;acronym title="Read the fucking manual"&gt;RTFM&lt;/acronym&gt; is all I answer to those.</description>
		<content:encoded><![CDATA[<p>The problem with <acronym title="Hypertext Markup Language">HTML</acronym> is, a whole bunch of wannabe-professionals with Frontpage 2003 earn their money, destroy the prices, quality and the idea behind the net. HTML is no secret, everyone may learn to code with accurate syntax - but they just don&#8217;t care.</p>
<blockquote><p>&#8220;What does this mean, there is no &lt;comment&gt;-tag? How do you do comments in html…</p></blockquote>
<p>And <acronym title="Read the fucking manual">RTFM</acronym> is all I answer to those.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark</title>
		<link>http://www.wiredvision.com/2005/11/16/call-yourself-a-web-professional/#comment-230</link>
		<dc:creator>Mark</dc:creator>
		<pubDate>Thu, 17 Nov 2005 03:58:15 +0000</pubDate>
		<guid isPermaLink="false">http://70.47.103.12/~wired/?p=90#comment-230</guid>
		<description>Okay, we probably shouldn't label those that don't practice Web standards as non-Web professionals.  They're just &lt;i&gt;bad&lt;/i&gt; Web professionals.

There are arguments above that people in different trades would still be considered professionals even if they aren't using the latest, cutting-edge techniques and tools.  Zeldman began preaching about standards in 1997, and A List Apart launched its CSS-based layout in February, 2001.  These are hardly new or "latest and greatest" concepts.

A true professional monitors the latest trends in his or her field, evaluates how they may fit, and hopefully experiments firsthand.  Almost five years later, this experimentation and honeymoon phase should be over in the professional arena.  Using standards isn't a bandwagon; it's the wagon we should all be driving in unison.</description>
		<content:encoded><![CDATA[<p>Okay, we probably shouldn&#8217;t label those that don&#8217;t practice Web standards as non-Web professionals.  They&#8217;re just <i>bad</i> Web professionals.</p>
<p>There are arguments above that people in different trades would still be considered professionals even if they aren&#8217;t using the latest, cutting-edge techniques and tools.  Zeldman began preaching about standards in 1997, and A List Apart launched its CSS-based layout in February, 2001.  These are hardly new or &#8220;latest and greatest&#8221; concepts.</p>
<p>A true professional monitors the latest trends in his or her field, evaluates how they may fit, and hopefully experiments firsthand.  Almost five years later, this experimentation and honeymoon phase should be over in the professional arena.  Using standards isn&#8217;t a bandwagon; it&#8217;s the wagon we should all be driving in unison.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Benson</title>
		<link>http://www.wiredvision.com/2005/11/16/call-yourself-a-web-professional/#comment-229</link>
		<dc:creator>Benson</dc:creator>
		<pubDate>Thu, 17 Nov 2005 00:03:06 +0000</pubDate>
		<guid isPermaLink="false">http://70.47.103.12/~wired/?p=90#comment-229</guid>
		<description>Agreed Richard. Current move to standard was only possible when IE improved on 5.0 and 5.5. CSS adoption was slow, but now we have browsers that can effectively use most (not all) of the standards set by W3C. So why not  move on to better ways than Table-Spacer hacks? There are just no excuses (unless its generated by CMS).

Its been two years now since the web have these new and better techniques to do thing why stay in the past? As for semantically coding HTML, there are no excuse but laziness not to learn it properly.

I used to teach design students on web design and first requirement is understand what you are doing in Dreamweaver and get a HTML and CSS book. This is not PhotoShop or InDesign, simply because Dreamweaver have not reached the point of perfecting WYSIWYG HTML/CSS. Maybe that will happen in the future but not now.</description>
		<content:encoded><![CDATA[<p>Agreed Richard. Current move to standard was only possible when IE improved on 5.0 and 5.5. CSS adoption was slow, but now we have browsers that can effectively use most (not all) of the standards set by W3C. So why not  move on to better ways than Table-Spacer hacks? There are just no excuses (unless its generated by CMS).</p>
<p>Its been two years now since the web have these new and better techniques to do thing why stay in the past? As for semantically coding HTML, there are no excuse but laziness not to learn it properly.</p>
<p>I used to teach design students on web design and first requirement is understand what you are doing in Dreamweaver and get a HTML and CSS book. This is not PhotoShop or InDesign, simply because Dreamweaver have not reached the point of perfecting WYSIWYG HTML/CSS. Maybe that will happen in the future but not now.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard Medek</title>
		<link>http://www.wiredvision.com/2005/11/16/call-yourself-a-web-professional/#comment-228</link>
		<dc:creator>Richard Medek</dc:creator>
		<pubDate>Wed, 16 Nov 2005 22:15:12 +0000</pubDate>
		<guid isPermaLink="false">http://70.47.103.12/~wired/?p=90#comment-228</guid>
		<description>&lt;blockquote&gt;Tables and spacer gifs were a necessary evil once, otherwise they wouldn’t have been adopted.&lt;/blockquote&gt;

What's your point here?  They &lt;i&gt;were&lt;/i&gt; a necessary evil &lt;i&gt;once&lt;/i&gt;.  Chopping off a leg in the case of infection was a necessary evil once in the field of medicine.  Are you saying compared to, say, penicillin that's still a viable option?

&lt;blockquote&gt;Also, I probably should have brought this up earlier, but knowing HTML on it’s own isn’t enough - even nowadays. You also need to know CSS to design a semantic, standards based design. CSS is harder to learn than HTML.&lt;/blockquote&gt;

That's a given.  How about server-side scripting, client-side scripting, visual and graphic design skills, and a background in effective UI?  Oh, not to mention the little things clients tend to expect, too, like SEO techniques, marketing options, and hosting and technical support.  Even more the reason why someone who calls themselves a "web professional" should be smart enough to understand the basics of semantic markup.

I'm sorry, but any "professional" who sticks to design techniques that slow down a site, increase maintenance time, and degrade accessibility because their techniques "worked" ten years ago... well, call them anything you want but I wouldn't hire them or see why anyone would.</description>
		<content:encoded><![CDATA[<blockquote><p>Tables and spacer gifs were a necessary evil once, otherwise they wouldn’t have been adopted.</p></blockquote>
<p>What&#8217;s your point here?  They <i>were</i> a necessary evil <i>once</i>.  Chopping off a leg in the case of infection was a necessary evil once in the field of medicine.  Are you saying compared to, say, penicillin that&#8217;s still a viable option?</p>
<blockquote><p>Also, I probably should have brought this up earlier, but knowing HTML on it’s own isn’t enough - even nowadays. You also need to know CSS to design a semantic, standards based design. CSS is harder to learn than HTML.</p></blockquote>
<p>That&#8217;s a given.  How about server-side scripting, client-side scripting, visual and graphic design skills, and a background in effective UI?  Oh, not to mention the little things clients tend to expect, too, like SEO techniques, marketing options, and hosting and technical support.  Even more the reason why someone who calls themselves a &#8220;web professional&#8221; should be smart enough to understand the basics of semantic markup.</p>
<p>I&#8217;m sorry, but any &#8220;professional&#8221; who sticks to design techniques that slow down a site, increase maintenance time, and degrade accessibility because their techniques &#8220;worked&#8221; ten years ago&#8230; well, call them anything you want but I wouldn&#8217;t hire them or see why anyone would.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Keith</title>
		<link>http://www.wiredvision.com/2005/11/16/call-yourself-a-web-professional/#comment-227</link>
		<dc:creator>Keith</dc:creator>
		<pubDate>Wed, 16 Nov 2005 21:34:34 +0000</pubDate>
		<guid isPermaLink="false">http://70.47.103.12/~wired/?p=90#comment-227</guid>
		<description>Tables and spacer gifs were a necessary evil once, otherwise they wouldn't have been adopted.

Also, I probably should have brought this up earlier, but knowing HTML on it's own isn't enough - even nowadays. You also need to know CSS to design a semantic, standards based design. CSS is harder to learn than HTML.

Regardless of how easy or hard HTML, CSS, semantics or web standards are to learn, I still don't think that those who practice web standards are entitled to say that those who don't practice it are not web professionals. Not yet.</description>
		<content:encoded><![CDATA[<p>Tables and spacer gifs were a necessary evil once, otherwise they wouldn&#8217;t have been adopted.</p>
<p>Also, I probably should have brought this up earlier, but knowing HTML on it&#8217;s own isn&#8217;t enough - even nowadays. You also need to know CSS to design a semantic, standards based design. CSS is harder to learn than HTML.</p>
<p>Regardless of how easy or hard HTML, CSS, semantics or web standards are to learn, I still don&#8217;t think that those who practice web standards are entitled to say that those who don&#8217;t practice it are not web professionals. Not yet.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
