Inside the Chin Crisis - The Final Hours


Comments
-
Thursday morning I contacted the CEO of Vanilla, his name is Luc. I explained the situation and described my frustration and confusion. He told me that he would look into it and get back to me. A few hours later, the chins/upvotes/downvotes started working again. Then I received the following email.
Hey Derek,
Luc alerted me to your message about support. For the last few months I've been acting as department head and I would like to take the time to address your issues. If you have any trouble in the future, please feel free to email me directly.
First I want to apologize for the seemingly sluggish nature of this bug being resolved. I appreciate that your users are passionate about the forums and enjoy its features. While we were eager to get this fixed, its important to understand that even very simple code fixes are dependent on everything that we may have lined up for a patch deploy being solidly reviewed. We've planned a deploy for today, and so you should see your issue resolved later this afternoon.
Support agents cannot always disclose what else could be waiting, as they might be security related, or be underlying structural changes for later features. This process is generally a 14 business day turn around. This month we've been specifically working on deploy processes, which has slowed things down. In the time where the risk of causing disruption outweighs the impact of the waiting bugs, we choose to keep the product stable.
We are looking to make this process faster and more reliable as we head into the new year, so I hope you'll find a general improvement of the time to resolve for reported bugs in the future.
That being said, I want to note that I encouraged Andrew not to read your users responses after my experience viewing your community. While we are committed to keeping our customers happy, I'm also responsible in making sure my employees aren't exposed to unnecessary, unprofessional hostility.
I hope this covers your concerns and restores some confidence in our process. I'm happy to answer any additional questions you have.
Thanks for your time,
-
Haha
Did you use the term "chins" in your message to the CEO?
What does vanilla actually refer to them as anyway?
-
"That being said, I want to note that I encouraged Andrew not to read your users responses after my experience viewing your community. While we are committed to keeping our customers happy, I'm also responsible in making sure my employees aren't exposed to unnecessary, unprofessional hostility."
@Crawfish? That shit's almost too good to be true -
Actually no, I said upvotes/downvotes. It would be difficult to explain the whole Jordan Chin - chincredible - chins history.Pitchfork51 said:Haha
Did you use the term "chins" in your message to the CEO?
What does vanilla actually refer to them as anyway?
It's hard. It's a process. It's not microwave popcorn. -
They referred to them as reactionsPitchfork51 said:Haha
Did you use the term "chins" in your message to the CEO?
What does vanilla actually refer to them as anyway? -
reaCHINS you say?DerekJohnson said:
They referred to them as reactionsPitchfork51 said:Haha
Did you use the term "chins" in your message to the CEO?
What does vanilla actually refer to them as anyway? -
*it’sDerekJohnson said:Thursday morning I contacted the CEO of Vanilla, his name is Luc. I explained the situation and described my frustration and confusion. He told me that he would look into it and get back to me. A few hours later, the chins/upvotes/downvotes started working again. Then I received the following email.
Hey Derek,
Luc alerted me to your message about support. For the last few months I've been acting as department head and I would like to take the time to address your issues. If you have any trouble in the future, please feel free to email me directly.
First I want to apologize for the seemingly sluggish nature of this bug being resolved. I appreciate that your users are passionate about the forums and enjoy its features. While we were eager to get this fixed, its important to understand that even very simple code fixes are dependent on everything that we may have lined up for a patch deploy being solidly reviewed. We've planned a deploy for today, and so you should see your issue resolved later this afternoon.
Support agents cannot always disclose what else could be waiting, as they might be security related, or be underlying structural changes for later features. This process is generally a 14 business day turn around. This month we've been specifically working on deploy processes, which has slowed things down. In the time where the risk of causing disruption outweighs the impact of the waiting bugs, we choose to keep the product stable.
We are looking to make this process faster and more reliable as we head into the new year, so I hope you'll find a general improvement of the time to resolve for reported bugs in the future.
That being said, I want to note that I encouraged Andrew not to read your users responses after my experience viewing your community. While we are committed to keeping our customers happy, I'm also responsible in making sure my employees aren't exposed to unnecessary, unprofessional hostility.
I hope this covers your concerns and restores some confidence in our process. I'm happy to answer any additional questions you have.
Thanks for your time, -
They still don't work right. I need to refresh to see them. I want that shit popping up asap
-
Hey @Pitchfork51 ,Pitchfork51 said:They still don't work right. I need to refresh to see them. I want that shit popping up asap
Luc alerted me to your message about support. For the last few months I've been acting as department head and I would like to take the time to address your issues. If you have any trouble in the future, please feel free to email me directly.
First I want to apologize for the seemingly sluggish nature of this bug being resolved. I appreciate that your users are passionate about the forums and enjoy its features. While we were eager to get this fixed, its important to understand that even very simple code fixes are dependent on everything that we may have lined up for a patch deploy being solidly reviewed. We've planned a deploy for today, and so you should see your issue resolved later this afternoon.
Support agents cannot always disclose what else could be waiting, as they might be security related, or be underlying structural changes for later features. This process is generally a 14 business day turn around. This month we've been specifically working on deploy processes, which has slowed things down. In the time where the risk of causing disruption outweighs the impact of the waiting bugs, we choose to keep the product stable.
We are looking to make this process faster and more reliable as we head into the new year, so I hope you'll find a general improvement of the time to resolve for reported bugs in the future.
That being said, I want to note that I encouraged Andrew not to read your users responses after my experience viewing your community. While we are committed to keeping our customers happy, I'm also responsible in making sure my employees aren't exposed to unnecessary, unprofessional hostility.
I hope this covers your concerns and restores some confidence in our process. I'm happy to answer any additional questions you have.
Thanks for your time, -
I'm not looking to antagonize when we already have a bad reputation
-
they've always been like thatPitchfork51 said:They still don't work right. I need to refresh to see them. I want that shit popping up asap
-
-
Then theyve always been shit!DerekJohnson said:
they've always been like thatPitchfork51 said:They still don't work right. I need to refresh to see them. I want that shit popping up asap
-
-
Chinappropriate commentary on our chinappropriate behavior.
It’s none of their fucking business. Just try to keep up to mediocre, Chinilla.
Thoseguysarefags.gif -
I'm also responsible in making sure my employees aren't exposed to unnecessary, unprofessional hostility.
This just made my morning -
Why does it always seem like it's the guys who don't donate that complain the most?Pitchfork51 said:They still don't work right. I need to refresh to see them. I want that shit popping up asap
-
The Chinobyl meltdown has been contained but the fallout continues. Glasnost was a Gorbachev thing but good to see Stalin trying.
-
Sounds like Luc needs to hire some non-pussies at Vanilla.DerekJohnson said:Thursday morning I contacted the CEO of Vanilla, his name is Luc. I explained the situation and described my frustration and confusion. He told me that he would look into it and get back to me. A few hours later, the chins/upvotes/downvotes started working again. Then I received the following email.
Hey Derek,
Luc alerted me to your message about support. For the last few months I've been acting as department head and I would like to take the time to address your issues. If you have any trouble in the future, please feel free to email me directly.
First I want to apologize for the seemingly sluggish nature of this bug being resolved. I appreciate that your users are passionate about the forums and enjoy its features. While we were eager to get this fixed, its important to understand that even very simple code fixes are dependent on everything that we may have lined up for a patch deploy being solidly reviewed. We've planned a deploy for today, and so you should see your issue resolved later this afternoon.
Support agents cannot always disclose what else could be waiting, as they might be security related, or be underlying structural changes for later features. This process is generally a 14 business day turn around. This month we've been specifically working on deploy processes, which has slowed things down. In the time where the risk of causing disruption outweighs the impact of the waiting bugs, we choose to keep the product stable.
We are looking to make this process faster and more reliable as we head into the new year, so I hope you'll find a general improvement of the time to resolve for reported bugs in the future.
That being said, I want to note that I encouraged Andrew not to read your users responses after my experience viewing your community. While we are committed to keeping our customers happy, I'm also responsible in making sure my employees aren't exposed to unnecessary, unprofessional hostility.
I hope this covers your concerns and restores some confidence in our process. I'm happy to answer any additional questions you have.
Thanks for your time, -
Same with owning a business. Complaints come primarily from "customers" who never spent a dime with you. Guys who need an itemized invoice before custom one-off work, I have learned to tell them they probably can't afford it.DerekJohnson said:
Why does it always seem like it's the guys who don't donate that complain the most?Pitchfork51 said:They still don't work right. I need to refresh to see them. I want that shit popping up asap
This doesn't sit well with the younger crowd so some like to post fake reviews.
It is hilarious. -
Do we have an embassy somewhere on Vanilla’s site we could lure these guys into?
-
POTMDennis_DeYoung said:Do we have an embassy somewhere on Vanilla’s site we could lure these guys into?
And look what you have created -
That being said, I want to note that I encouraged Andrew not to read your users responses after my experience viewing your community. While we are committed to keeping our customers happy, I'm also responsible in making sure my employees aren't exposed to unnecessary, unprofessional hostility.
-
Seriously so when we DM @Vanillatest or PM to the Devs, they actually read that shit?
-
Soft. Millenial. Fags.GrundleStiltzkin said:Seriously so when we DM @Vanillatest or PM to the Devs, they actually read that shit?
-
French. Canada.GrundleStiltzkin said:Seriously so when we DM @Vanillatest or PM to the Devs, they actually read that shit?
-
Do they not like our? money?DerekJohnson said:I'm not looking to antagonize when we already have a bad reputation
-
Hey man that's where the tuff guys come fromAZDuck said:
French. Canada.GrundleStiltzkin said:Seriously so when we DM @Vanillatest or PM to the Devs, they actually read that shit?
-
The devs can't stop looking now that they have seen the belly of the beast here
-
“Ninja...please” would have been the proper response back to that shitDerekJohnson said:Thursday morning I contacted the CEO of Vanilla, his name is Luc. I explained the situation and described my frustration and confusion. He told me that he would look into it and get back to me. A few hours later, the chins/upvotes/downvotes started working again. Then I received the following email.
Hey Derek,
Luc alerted me to your message about support. For the last few months I've been acting as department head and I would like to take the time to address your issues. If you have any trouble in the future, please feel free to email me directly.
First I want to apologize for the seemingly sluggish nature of this bug being resolved. I appreciate that your users are passionate about the forums and enjoy its features. While we were eager to get this fixed, its important to understand that even very simple code fixes are dependent on everything that we may have lined up for a patch deploy being solidly reviewed. We've planned a deploy for today, and so you should see your issue resolved later this afternoon.
Support agents cannot always disclose what else could be waiting, as they might be security related, or be underlying structural changes for later features. This process is generally a 14 business day turn around. This month we've been specifically working on deploy processes, which has slowed things down. In the time where the risk of causing disruption outweighs the impact of the waiting bugs, we choose to keep the product stable.
We are looking to make this process faster and more reliable as we head into the new year, so I hope you'll find a general improvement of the time to resolve for reported bugs in the future.
That being said, I want to note that I encouraged Andrew not to read your users responses after my experience viewing your community. While we are committed to keeping our customers happy, I'm also responsible in making sure my employees aren't exposed to unnecessary, unprofessional hostility.
I hope this covers your concerns and restores some confidence in our process. I'm happy to answer any additional questions you have.
Thanks for your time,