|
|
Posted by Adrienne on 06/15/05 10:10
Gazing into my crystal ball I observed Travis Newbury
<TravisNewbury@hotmail.com> writing in news:ccIre.589$mD6.108@fe07.lga:
> Simon wrote:
>> I know that a site that validates is a good site, because it follows
>> the rules given by W3c.
>> But I am about to employ a web designer/programmer should I
>> automatically reject them if their site does not validate?
>> Should I expect the site created by them to validate?
>
> You should evaluate them on the ability to get the job done the way you
> need it to be done. If every site they have ever worked on validates
> or not is completely irrelevant. Can they make the site that you need
> them to make? If so, then they are a candidate for the position.
>
I have to disagree with you there. You can buy a brand new car, but it
turns out to be a lemon because no one looked under the hood. Same thing
with a site. The site may look great, but the underlying markup, and/or
server side coding could be a mess. Making changes to it in the future
could be costly in terms of time and money.
Trust me, I know. Nothing like nested tables and nested includes with no
commenting.
--
Adrienne Boswell
http://www.cavalcade-of-coding.info
Please respond to the group so others can share
Navigation:
[Reply to this message]
|