Yep, although you might want to make sure and wait for another member here to confirm this as I am not completely sure. Better yet, why don't you call the iPage guys because they can give you an answer better...
Jeess, hardcore hey!!!, depends , there's lots of things that could affect it really, say size of company, position of the job etc. But be sure these days it's not going to be just html, expect to be asked about your knowledge on css, ssl, ssi, photoshop/illustrator possibly, cgi, flash etc, but ofcourse all depends on the job description, you could be just purely working with html while you have a load of companions that will just do the flash side, ssi side etc..
Heres a couple of job requirements that came under html coder on a yahoo search:.
HTML coder vacancy:.
Html coder at digital arts group:.
Html/css — exellent knowledge;.
Experience of html-coding;.
Skill to work with the text..
Knowledge of Internet protocols..
This position is also responsible for ensuring cleanliness and optimization of all HTML on the site.
Looks like they want someone who knows how to validate their code..
Let us know how the interview goes. And also let us know if anyone at any time asks any questions about validated code. I've never had the experience in my IT career.... but there could be a first..
I severly doubt that they want someone to run code through a validator all day. More than likely, they want results that make things work.... but who knows?..
Seeing as we're talking about validated code.... does it really matter that much?? the first few websites I did looked grand and worked no problems but when I later on checked them in the validator they had tons of errors!!.
What are the consequences, if any, of code not being validated?..
It depends what the errors are..
If it is tags or attributes spelt incorrectly like.
<img witdh="100" hiehgt="100">.
Then the code isn't going to work..
If it is nesting errors like.
Then the code will produce different results in different browsers..
If the stuff highlighted is just some.
, then you'll be aware that the code only works in some browsers and fails in others..
Don't play Russian Roulette with your code by just checking that it works in a single version of Internet Explorer and then hoping for the best. Run it through a code checker, fix as many of the errors as possible, and benefit from a iPage site that will work on a greater range of browsers...
I just use the validator to make sure I didn't improperly nest tags or forgot to close a tag... fairly serious errors like that..
If the validator *****es about something like <embed>, saying that it's an error, who cares. Can't rely on the validator all the time. A page that doesn't validate doesn't mean it won't look good with Netscape/Opera/etc...
If the validator *****es about something like <embed>, saying that it's an error, who cares. Can't rely on the validator all the time. A page that doesn't validate doesn't mean it won't look good with Netscape/Opera/etc..
Hmm, I think that is exactly what I was saying..
Check this thread out:.
In particular this post:.
And this validator link:.
To see what I mean...
I found this old VHS tape where these two <table> tags, from W3C, got all nested wrong with this <td> tag from some new dot com venture... well this Swedish pipe music started playing in the background... you know the stuff 1970's elevator music. Well I love to describe it more but I was almost sick. That poor little <td> tag. I had to turn it off.
Is that hardcore enough? Oh the nurse is back with the crayons... I have to go...
All this stuff about jobs... has anyone read the post I made in the feedback section about a little sub forum for career advice and what not? Your thoughts there would be welcome...