Sponsored by ShareChat
Full-time open positions at ShareChat
ShareChat is looking for full-time Backend, Android, Machine Learning Engineers and Web Developers to be a part of their team. These positions are open for professionals across the globe. Click here to know more about the open positions. Compete in the contest and apply to be a part of ShareChat.
ShareChat is a social network for the next billion smartphone users. They have grown organically to 18 million active users and are doubling every 4 months. Currently, their userbase is majorly from India, Sri Lanka, Bangladesh, Nepal, Kuwait, Qatar, UAE, Canada and are expanding at a very rapid pace. We are happy to associate with ShareChat and would like to announce that they are the official sponsors for the January Long Challenge 2019. Through this contest, they are also providing full-time opportunities with lucrative offers. Interested programmers can go through the above mentioned application link.
New users are requested to go through the below information to know more about the contest.
CodeChef: A Platform for Aspiring Programmers
CodeChef was created as a platform to help programmers make it big in the world of algorithms, computer programming, and programming contests. At CodeChef, we work hard to revive the geek in you by hosting a programming contest at the start of the month and another smaller programming challenge in the middle of the month.
About CodeChef January Long Challenge:
CodeChef Long Challenge is a 10-day monthly coding contest where you can show off your computer programming skills. The significance being - it gives you enough time to think about a problem, try different ways of attacking the problem, read the concepts etc. If you’re usually slow at solving problems and have ample time at hand, this is ideal for you. We also put in a lot of efforts in getting quality problems, which would, in turn, foster your learning while solving them.
- Duration: 10 Days, from 4th January 1500 hrs IST to 14th January 1500 hrs IST. Check your timezone here.
Eligibility Criteria: Anyone with a knack for Programming :P
Our contests are open to all the programmers across the globe.
What's in it for you?
The idea behind these programming contests is that we want you to learn while competing. Also we believe that it is alright to refer to tutorials, books and other materials, learn a concept and then apply the same to solve a problem during a contest. But it is not alright to copy other people's solutions or seek other people's help to solve a problem without understanding it. The dividing line may seem to be thin but it can be captured by the spirit of learning. If whatever you are doing is making you learn while you do so, we tend to believe that it is alright. However, all the participants are expected to abide to CodeChef Code Of Conduct
Not just that, as a token of motivation we also give away cash prizes and goodies to the winners of the contest. However, our sole intention lies in making our users learn new concepts while competing. You can know more about prizes here. FYI, here are the list of cash prizes:
- 1st prize: INR 12000/-
- 2nd prize: INR 8000/-
- 1st prize: $400
- 2nd prize: $300
Rules and Regulations:
- Please do not discuss strategy, suggestions or tips in the comments during a live contest. Posting questions clarifying the problem statement is ok. If you are unsure, email us at email@example.com.
- All the problems will be partially graded and you will get a score for passing certain test data (except tie-breaker problem). You will receive hundred (100) point for solving a problem (passing all test cases).
- The details of the failed test cases will also be visible on your solution page (except challenge problem)
- There are no penalties for incorrect submissions.
- Each contest will have one min/max tie breaker problem, where the best solution will receive one point and all other solutions will receive a fraction based how close they come to the best solution.
- You shall not possess more than one account on CodeChef. If you have, then do let us know, so that we can deactivate the insignificant one. If you do not report it and we come to know about it, we may deactivate both the accounts permanently.
- The score that you will see during the contest (for tie-breaker problem), will only be partial (obtained on 20% of the test data). The submissions will be re-judged at the end of the contest to get a full score (obtained on the whole test data).
- Similarly, for the challenge problem, the time and memory consumption shown for a submission will be the maximum of the corresponding metric on only the 20% of the test files on which it is being scored now. You will still get a WA/TLE/MLE verdict if your submission fails in the remaining 80% of the test files.
- The number of submissions that one can make during the contest on the problem will be limited to 500 and the maximum number of submissions allowed in the challenge problem are limited to 100.
Note: You can now "Code, Compile, and Run" your codes on our newly launched Online IDE.
However, if you are using any other online development environment, make sure that other contestants don't have access to your code. As a contestant, you are responsible for making sure others don't access the code that you submit. If you use Ideone, make sure to mark your submission "private" (not secret)".
14th January, 16:00 IST: The January Challenge 2019 has ended!
The editorials can be found here.
The problems have been moved to the practice section.
Solutions are public for all the problems.
MOSS results are not out yet. Ranklist will be recalculated and Laddus will be provided post the MOSS process.
11th Jan 2019, 6:29 PM IST: One more test case in MXDIST added, all submissions rejudged, sorry for the inconvenience.
8th Jan 2019, 9:40 AM IST: The sample data in GRAPART has been changed.
5th Jan 2019, 6:29 PM IST: The constraints on N, Q, xi, yi in 2 and 3 subtasks of MXDIST were increased, sorry for the inconvenience.
4th Jan 2019, 4:05 PM IST: A draft version of the XYPIZQ problem statement had been uploaded by mistake. It has been fixed now.