Here’s a reason to know and use strict-compatible code and Web standards: because you can’t get a job with my agency if you don’t.
Arguments about how non-strict and non-standards compliant code work just fine and nobody cares will eventually begin to ring hollow when more and more employers, like mine, begin to insist on competent coders rather than make-do coders.
Sure, sloppy and deprecated code works most of the time. But it might be good to think about if you’ll be working most the time – or losing job opportunities to those who care about this stuff.
Andy Rutledge
Here’s a reason to know and use strict-compatible code and Web standards: because you can’t get a job with my agency if you don’t.
Arguments about how non-strict and non-standards compliant code work just fine and nobody cares will eventually begin to ring hollow when more and more employers, like mine, begin to insist on competent coders rather than make-do coders.
Sure, sloppy and deprecated code works most of the time. But it might be good to think about if you’ll be working most the time – or losing job opportunities to those who care about this stuff.