You are not logged in. Please login at www.codechef.com to post your questions!

×

Why doesn't the Codechef do something about the sloppy Cook-Offs?

0
1

I have always liked codechef because of its platform. But since CookOff47, it has been a constant source of discouragement!
I also posted my query at FB event, but it seems like it got deleted. Huh, can't handle criticism, let alone be critique!
alt text And last saturday, CookOff67 started off as a real disheartening. I seriously think, Codechef/DirectI anyone who can do something to promote coding culture in India, should see to it that such technical glitches are resolved.

asked 25 Feb '16, 01:53

abcdexter24's gravatar image

2★abcdexter24
309212
accept rate: 3%

edited 16 Mar '16, 18:12

admin's gravatar image

0★admin ♦♦
19.8k350498541


@abcdexter24: Regret that this happened. There are a couple of issues that you have raised. Let me try and answer them point wise.

  1. Technical Glitch - We are certainly aware of this and have done quite a few things to fix a lot of glitches that we have faced in the past. However, we agree and we apologise that we goofed up once again. Just to let you know, this was not because of any of the past reasons. It was not a load issue which has plagued us in the recent past. If you see, once the contest started, things went smooth. Not that I am trying to take any credit for it. This is how it was expected to happen from the start and it was unfortunate that it did not. The reason is not something that me or my team can take pride in. There was a change of credentials that did not propagate in our settings file and we did not notice that this caused the problems not to be moved on the contest page. It took us a while to figure this out during the contest and fix it. May sound dumb! And yes, that may not even seem to make much sense. Let me just say that there is a lot of baggage that we carry from legacy and hence it is not the best possible architecture that we have at present. We are moving ahead step by step, learning from our mistakes. And trust me when I say that the mistakes are different. In the past couple of CookOff's we were breathing a sigh of relief that things have improved only to feel fooled once again. Hopefully, the day is not far when the automation that we are bringing in and the effort that we are putting in will also reflect in smooth conduction of our CookOff's on a more consistent and sustained basis.

  2. Handling Criticism - I think it is unfair for you to say so. Let me, in my capacity of heading CodeChef for the last 6 years, categorically assert that we never ever delete comments; unless they are abusive and inappropriate for anyone in our target audience to view. Let me be frank in sharing with you that the amount of flak that we have received in the last 6 years is quite a lot and all of that is safely saved on our blogs, social media channels and emails. None of it has ever been deleted. Just as an example you can read a lot of criticism here: https://www.facebook.com/CodeChef/posts/10153108220472799. And they are quite scathing. They remind us of our mistakes and keep us on our toes. We have valued every single feedback, both good and bad. I do not know how your comment got deleted. It may have been through a mistake (either yours or one of us, admins), or a technical glitch.

We accept that we goofed up once again and we are fixing things. I would like to believe that we have come a long way in this and the differential that we need to cover is not as big as it appears right now. Your feedback and your participation is very valued. It shows that you care. And there cannot be anything more valuable for us. I want to assure you that we are concerned too and we are fixing things. You will see the results soon.

link

answered 25 Feb '16, 18:00

anup's gravatar image

2★anup ♦♦
2.2k273943
accept rate: 23%

1

Ok, i hope to do better the next time ^_^ Thank you for your detailed answer, if shows that you take constructive criticism seriously.

(28 Feb '16, 19:32) abcdexter242★

The situation in the last cook-off was not nearly as bad as in e.g. Aug15 (I didn't take part in 2014, so I can't tell about COOK47). After the initial glitch there was a fair and smooth contest (just half an hour later than expected). AFAIK no one was able to see the problem statements in the beginning so no harm was done. By delaying the contest by half an hour, Codechef did the best they could do in that situation. So while not being optimal, I don't think any one should be discouraged.

Compared to that Aug15 was a completely different situation. Some got the problem statements, some didn't or had to try several times. Same for submissions. And it wasn't obvious whether Codechef would be able to fix all those problems - but luckily they were.

link

answered 25 Feb '16, 12:03

ceilks's gravatar image

7★ceilks
1.8k9
accept rate: 36%

toggle preview
Preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported
  • mathemetical formulas in Latex between $ symbol

Question tags:

×2,345
×554
×87
×16

question asked: 25 Feb '16, 01:53

question was seen: 2,078 times

last updated: 16 Mar '16, 18:12