The final season was great too, though. I really enjoyed it. But, dear god, I'm trying to recall other shows that tanked so bad second year--Heroes? Eureka didn't stink until year 3, and it recovered too. Not Heroes, sadly. We'll just deem those seasons the TV versions of (Highlander 2) (you have to whisper it, or you'll catch it on TV and be forced to watch...).
Zulilly has Adirondack chairs! I can't believe I'm waffling on whether or not I want to wait their forever shipping times. Because, you know, summer will be over in 16 days. But for $90--sheeit, the original cost at Cost Market was $80. And it's got a nice natural finish: [link] Yeah, I'ma do it.
![[link]](http://mcdn.zulily.com/media/catalog/product//11736/LEIGHCOUNTRY_TX94056_1371070073.jpg.){kind=link}
Getting that URL just reminded me. We have a web team that's not in IT, they're marketing. They focus on client side technology, although they do have some back end knowledge. Their tools are HTML, CSS, and Javascript. In IT, we have programmers whose output is HTML, but that doesn't mean they know (or care about) it.
The web team designed an error page that IT was to implement. It said "Our apologies..." But the O was actually the lens of a magnifying glass. I give the developer the HTML and image, and he comes back with a page that says "ur apologies" and asks me if it's right.
I'm sorry, what? How is this a question? Do you not even look at the screen?
I asked him where the image was, and he said there was no image. I start opening the HTML, and he says "No! There was no image tag!" He's right--the image was a table background. But it was *there* in the HTML I gave him, and not there in what he gave me back. So he took it out. On purpose. It was a thing that he did.
HOW DO YOU DO THAT??? How do you think those results are good enough to show anyone? Do you not wonder why I sent you an image with a filename that matches some weird parameter in the HTML? I mean, assuming you don't know HTML well enough to know that tables can have image backgrounds, which is...that's not excusable, IMO.
This is his job. He's a .NET developer, and his output *is* HTML. He's writing a web application! Front and back and middle end! But he thinks "ur apologies" is good enough.
That's what I worry about with some of the copy that gets to me. That someone thought "enh--good enough."
No! We're supposed to be better than good! Let's aim for excellent!
If I told that to his manager, she'd hold it against me for bringing it up. "What am I supposed to do with that information?"
Oh, and this was not the incompetent developer. This was the most senior developer working on this product that's most used by thousands of our users.
Okay, that was clearly festering. Back to slide deck.