Adrienne said:
Jenn, the validator is your friend. It was written by the W3C, the
folks who make up the standards the rest of us keep going on about.
True, validation is not the be all to end all, but when something
doesn't work right, the first place to check is with the validator.
I've never used a validator in the 14 yrs I've been making websites.
Occasionally, I have seen a person here or there talk about them, but only
here have I heard of any necessity of using them. How many people post here
on average? If it is such a necessity, why have I not heard of it being so
important until 14 yrs after the fact? I'm not saying it doesn't exist...
I'm saying in the 14 yrs I've been doing this no one has cared to inquire if
a site validated with W3C.
Having a well marked up document makes it easier for everyone, search
engines and assistive technologies. Tables, unless they are used for
tabular data, can be prolematic for asssistive technologies, as they
often do not read the content in the way a visual person would
perceive it. Have a look at section 508 of the Americans with
Disabilities Act. Should you ever have client who must abide by those
rules (eg. government, some non-profits, etc.), you, as the designer,
would be held responsible.
I know you are convinced of what you are saying, but it's not going to stop
me from using tables because I like the control they afford when building
content. It's a basic technique that works even when other techniques
consume time just trying to figure them out.
Having your documents validate to standards shows others that you, as
a professional, take pride in your work.
No one I know of cares about the code... all they care about is what they
see and if it works or not and is completed by it's due date.
Make no mistake.. I take pride in my work, and I work very hard to give my
clients what they ask for... I've spent many long hours studying on my own
and playing with code just for the sake of practicing it. I even took one
summer to learn vb and vb.net and write my own desktop program just to see
if I could do it. Next, I studied about 6 months to learn Visual Studio
and T-sql so I could build databases. I already was familiar with that
somewhat because the backend of Access uses a similar language and interface
as sql (but my Access version was older than the Visual Studio that I
studied.) I learned all of this in books and countless tutorials, I did it
all on my own. I worked hard for years when my kids were growing up, and
learned a skill that I could earn a decent wage at, and I have been
successful. I couldn't go to school because I was the teacher, mother, and
whatever else my family needed when we were raising our kids and
homeschooling them - 3 of them - I homeschooled for approx. 19 yrs total.
When I was hired for my first "real" job I finally made enough money to buy
groceries on a regular basis and buy clothes for my kids at Walmart instead
of buying second hand clothing for them all the time. I had that part-time
job for like 4 yrs. Do you know what it is like to finally be able to tell
your child... "Yes you can have that brand new dress or pair of shorts?"
When I got my present job I was so happy that I would cry every day on the
way to work because I was so greatful to have it. You have no idea what it
really means to have pride in your work until you've spent a lifetime
studying by yourself in hopes that some day you will be able to earn a
living.
Some of you people here (not necessarily you Adrienne[this post is actually
one of the nicer posts I've seen so far) seem to be so happy to put me down
and get your digs in because I haven't done it like you would do it... my
code isn't what you think it should be... an inanimate thing seems to have
more value than a human being has to some of you...... but until you've
walked a mile in my shoes, I have to wonder how you could be so cruel and
mean to someone you don't know in the name of code?