A List Apart: Articles: Where Our Standards Went Wrong
Popularity Report
![]() |
|||
![]() |
|||
![]() |
|||
![]() |
|||
![]() |
|||
![]() |
URL Tag Cloud
- standards
- , css
- , webdesign
- , salespeech
- , webstandards
- , accessibility
- , sales
- , xhtml
- , article
- , webdev
- , web
- , html
- , design
Bookmark History
Saved by 3 people (0 private), first by anonymouse user on 2007-03-18
- Egonbianchet on 2008-03-21 - Tags webdesign , webstandards
- Meratspain on 2007-03-18 - Tags css , sales , salespeech , standards
- Vanderwal on 2007-02-28 - Tags article , css , design , html , standards , xhtml , webdev , webdesign , web , accessibility , business
Public Sticky notes
Highlighted by meratspain
Highlighted by meratspain
Toward the end of my first year in business, I noticed that more and more of my time was spent working around invalid code. Layout issues that would have been trivial to fix in a valid, error-free template would take significantly longer to debug in a live page that had a few hundred validation errors. It was a matter of figuring out which parts of the page weren’t causing the errors, so I could focus on fixing the problematic section. But when the page’s markup has three or four hundred validation errors, this process quickly becomes a time sink. A necessary one, but a sink nonetheless.
So by year’s end, I found that approximately fifteen percent of my time was spent mired in invalid code
Highlighted by egonbianchet


Public Comment