Azure Jane Lunatic (Azz) 🌺 (
azurelunatic) wrote2012-12-05 12:48 pm
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
This is a bad practice and you should not do it:
I am still very angry with whatever dick in product management felt that it was necessary or appropriate to combine the following two sentiments:
"I am so excited about the upcoming product release! The date has been pushed up! THIS IS WONDERFUL!"
"In order to accommodate the upcoming early release of this product, some features were dropped. This very popular feature was one of them."
This results in "I'M SO HAPPY YOU'RE NOT GETTING THE FEATURE YOU NEED TO DO WHATEVER IT IS THAT YOU DO, BUT AREN'T YOU GLAD YOU'LL BE GETTING A NEW CRAPPY VERSION SOONER?"
No. No, I am not happy, and I am angry that you are so happy about this. Please go rinse your inbox with an appropriately destructive kind of acid, and let's never speak of this again.
When announcing something that you know is going to be bad news, on the ticket for the feature in question, the early release of version mango-shitting-cockatoo (the upgrade from destructive-parrot) is a neutral thing at best, not a good thing. You can be as exited as you want on the main blog, or in the press releases, and you can link to the main blog or press releases, but on the bug itself, this is a neutral thing.
It might even be appropriate to apologize for the inconvenience and disappointment. But "I'm excited to announce", multiple exclamation points, and "cheers" in the ticket itself? What the actual fuck, man.
"I am so excited about the upcoming product release! The date has been pushed up! THIS IS WONDERFUL!"
"In order to accommodate the upcoming early release of this product, some features were dropped. This very popular feature was one of them."
This results in "I'M SO HAPPY YOU'RE NOT GETTING THE FEATURE YOU NEED TO DO WHATEVER IT IS THAT YOU DO, BUT AREN'T YOU GLAD YOU'LL BE GETTING A NEW CRAPPY VERSION SOONER?"
No. No, I am not happy, and I am angry that you are so happy about this. Please go rinse your inbox with an appropriately destructive kind of acid, and let's never speak of this again.
When announcing something that you know is going to be bad news, on the ticket for the feature in question, the early release of version mango-shitting-cockatoo (the upgrade from destructive-parrot) is a neutral thing at best, not a good thing. You can be as exited as you want on the main blog, or in the press releases, and you can link to the main blog or press releases, but on the bug itself, this is a neutral thing.
It might even be appropriate to apologize for the inconvenience and disappointment. But "I'm excited to announce", multiple exclamation points, and "cheers" in the ticket itself? What the actual fuck, man.
no subject
That made me choke on my cookie.
no subject
no subject
I am typing this on Insecure Iguana.
no subject
no subject
no subject
no subject
no subject
[I kid you not, there's a sys-admin of my acquaintance that has one of those hanging on his cubicle wall. No-one has asked him about it... EVER]
no subject
no subject
no subject
no subject
I hate it when they say "there's X problem, it's important to fix it", only give you a fragment of the data to reproduce, and then escalate it to three levels up the food chain 6 days after they've stuck it unannounced in your queue with some BS subject and BS product, and you aren't even the correct property for the bug to begin with!!! Seriously, my job does not involve coding/designing or deploying web pages, don't give me html/css bugs.