,
7 tweets,
2 min read
Read on Twitter
this is the mcdonalds 80" television menu in the drive through this morning 
i didn't edit this, it really looked like that. and i promise you i know exactly why: it's because this is a webpage, that text is populated by javascript, and someone made a tiny error. and nobody proofread it.
had this been a static image crafted individually for every market - the way chain restaurants have done signage for half a century - a standard creative process with a proofreader would have been used and this almost certainly would not have happened
but because this is a computer program for some reason, the task "be one sign for 8 hours and then become another one for 16 hours", the simplest thing imaginable, managed to fail. if this was two jpegs on a slideshow with a timer it wouldn't. but this is a webpage, no question.
"why does it matter that it's web tech specifically" because web enables people to bang out stuff that looks finished and reliable so fast that waiting for UAT/QC looks like an absurd waste of time.
also nobody would ever have done this in native code. it's just too inconvenient. perhaps if silverlight or WPF or something had taken off more, but they didn't. if you want something like this ready to use in a single day, it's gonna be web.
the beef i have with web is less practical and more pragmatic: i just tend to see garbage code that was obviously never thoroughly tested. i don't really care about the why.
