The last paragraph of Wired’s article “Browsing Around for New Targets” caught my attention:
But one HTML contractor, who asked not to be named, illustrated the uphill battle the WaSP faces in getting programmers to lay aside their old browser-specific tricks: “Do you know how much I get paid for knowing this stuff?”
Yep. And can you imagine how much more you’d be paid if you knew how to code to standards, thus delivering a superior product with outstanding delivery capabilities? Not to mention what kind of reputation you’d build up for doing so, and how much more you could charge then?
Actually, it occurs to me that something the WaSP ought to do (if they haven’t already; we’ll find out tomorrow) is create an executive-level whitepaper that basically says, “If you’re still shelling out for multiple versions of a site and 80KB HTML source, you’re paying way too much for way too little. Stop paying people to know how browsers worked two years ago, and start paying for people who know how to make your site work two years from now.”