问题描述
即使我总是努力获得完整的验证，我经常想知道这是否浪费时间。如果代码运行，它在所有浏览器（我使用browsershots.org验证）看起来是一样的，那么我需要再进一步或者我只是过度肛门？
Even though I always strive for complete validation these days, I often wonder if it's a waste of time. If the code runs and it looks the same in all browsers (I use browsershots.org to verify) then do I need to take it any further or am I just being overly anal?
在您为以下内容创建代码时，您拥有的代码级别：
What level do you hold your code to when you create it for:
a）自己
b）客户
a) yourselfb) your clients
PS Jeff和公司，为什么不堆栈溢出验证？ ：）
P.S. Jeff and company, why doesn't stack overflow validate? :)
编辑：一些很好的见解，我认为，因为我一直这么有效的痴迷了这么久我的程序知道什么会导致问题和什么不会，因此我比首先创建网站，然后返回并修复验证问题的用户处于更好的位置。
我想我可以发布另一个问题堆栈溢出; 你在你走，或你完成，然后回去并验证吗？
I think I may post another question on stack overflow; "Do you validate as you go or do you finish and then go back and validate?" as that seems to be where this question is going
推荐答案
a）必须看起来一样
b）尽可能符合标准，但不要肛门阻止整理工作
b) As standards-compliant as possible, but not so anal that it blocks finishing work
在你有永久性访问代码，我不认为标准合规是重要的，因为你可以随时更改代码，如果有什么断裂。如果你没有永久访问（即，你签署的代码，它成为别人的责任），最好是作为标准兼容，尽可能减少维护头痛后，即使你从来没有再次处理代码，您的声誉仍然存在，可以传输到其他潜在客户，许多团队喜欢指责以前的开发者出现的问题。
In a situation where you have perpetual access to the code, I don't think standards-compliance is all that important, since you can always make changes to the code if something breaks. If you don't have perpetual access (ie, you sign off on the code and it becomes someone else's responsibility), it's probably best to be as standards-compliant as possible to minimize maintenance headaches later... even if you never have to deal with the code again, your reputation persists and can be transmitted to other potential clients, and many teams like to blame the previous developer(s) for problems that come up.
这篇关于完成工作时，W3C XHTML / CSS验证有多重要？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！