Hello 2015! Hello Codeforces!
It seems it is time to take stock. Frankly, I was almost feared to start summing statistics of 2014. In 2013 Codeforces showed rapid growth so that it would not be surprising to look bad on the background of 2013. Certainly not! I was pleasantly surprised by the statistics and reports!
Just below is a list of major events and achievements of Codeforces over the year. For you, it's just a list, but please note — every item includes hard work of multi-day Codeforces team, writers of problems, the organizers of contests and tournaments, problem testers and volunteers. Yay! Together we have done all of this:
- introduced Codeforces API
- added (and sometimes improved) all Andrew andrewzta Stankevich contests
- Codeforces supported mode to work as iframe-widget, and Codeforces helped Google to run https://www.calltocode.ie/ for Ireland high school children
- nearly 70 rounds have been hosted for our beloved users
- nearly 450 new and interesting problems were prepared for the contests on the Codeforces platform
- supported new programming languages
- together with CROC was held Coder-Strike 2014
- hosted April Fools Day Contest 2014 from magnificent Maria Nickolas Mykhailova
- together with the jury of Russian Code Cup 2014 held RCC Warmup, who opened the RCC for a wide range of Codeforces users
- Codeforces played a role of press-partner of RCC, ACM-ICPC Finals in Ekaterinburg, Yandex.Algorithm
- we held ZeptoLab Code Rush 2014 (Om Nomes!)
- helped wonderful company RocketFuel to run Rockethon 2014 (on Codeforces)
- hosted MemSQL Start [c] UP 2.0 with the finals the MemSQL office!
- had 11 episodes of Codeforces Trainings Season 02
- together with the jury Bayan Contest held Bayan Contest Warm Up
- updated Polygon (http://polygon.codeforces.com/) introducing an infinite number of small improvements
- supported tutorial in Polygon
- file system queries caching in Polygon has led to significant acceleration of most pages
- together with GridDynamics held GridGames (for Saratov university students)
- broke all records: 6274 registrations on Good Bye 2014!
In this cold January day, I send warm greetings to the Codeforces team and our friends: developers, problem coordinators, problem writers, testers, tireless bloggers and all of you — the knowledge-hungry competitors!
And here is a comparison with previous years of Codeforces. Clearly. In Pictures.
Number of registered users (we've introduced captcha — it didn't affect growth much)
Searches of codeforces in Internet (trends.google.com)
Active contestants (took part at least once in July-December of a year)
Number of submissions (attempts)
Number of unique visitors (from GoogleAnalytics)
Number of visits (sessions) (from GoogleAnalytics)
Number of pageviews (from GoogleAnalytics)
P.S. Even I was surprised by statistics of 2014. There is a selfie in the moment when Good Bye 2014 registration ends.
Thank you and all Codeforces team for all of these improvements and contests. Codeforces is a really friendly, lovely, wonderful and useful community.
I think this Impressive success and great results return to yours noticeable Dynamism which i have not seen before in any other online judge (TopCoder , CodeChef , SPOJ , ..etc). Like Changing the Good Bye 2014 contest to be division combined based on the desire of participants, changing handles which is made annually and lately the amazing magic item which allows us to change our rank for a few days . Really Codeforces is the loveliest platform i've ever seen. Thank You Codeforces team.
I think the most important aspect of Codeforces contributing to its success relative to TopCoder and other judges is its extreme user-friendliness. Everything; problem set, upcoming contests, gym, contest announcement posts, are easily found on this website, unlike many other judges (specifically TopCoder).
Is "Active contest participants" stats adjusted to take into account fake accounts created for Div 2-only contests, or is it a raw value?
Yes, that was an impressive registration for the end-of-year contest! You picked the perfect time for it.
I do have a comment about "active participants". I think the "top rated" list that appears on the home page of codeforces should really be a "top rated active" list. Many of them in the list have not done a contest in half a year, and one of them has not done a contest in 1.5 years. Probably requiring a contest every 2 months would be a good requirement to be shown there.
I also agree. On top of this, I would like to suggest the idea of "rating decay". Say if you have a rating of more than 2200 (or maybe even 1700), your rating will automatically decrease by 5-10% every 2-3 months you don't participate in a contest. Again, numbers can be adjusted, but this is just an idea. This way, in order to stay red/div1, you need to be at least semi-active, and this can also deal with some of the rating inflation.
Also, We can have some kind of "monthly top rated" list which is for top users with most increasing in their ratings. It can be a good motivation for beginners or even non-IGM users!
I afraid that it can give motivation for some reds to create new account and show bright performance. Something like why they take part in Div2 rounds from fake accounts. Maybe it is good idea to include in such nominations only verified account, but verification process is hard to implement and support.
It seems fake accounts are inevitable but i think it worth to have such list.
Maybe some other criteria such as participating in some minimum number of rated contests can decrease number of fake accounts in the list.
Thanks! I agree that it is good idea to leave only "active" participants in default view of ratings page. I don't like "requiring every 2 months", I think topcoder's 6 months is OK.
It contains all the users. Do you know really reliable way to detect fake div-2 only accounts?
I would imagine it's admins' job to detect them using all information available to them, not participants'. The keyword is "data mining". You could even run a predictive contest — given statistics of people participating in contests, predict whether they will participate again any time soon :-)
Thanks to all Codeforces for these contests and improvements! I can't wait to see what is in store in this brand new year 'A'*('!' — 2) !
Every year better than last year! Good luck and thanks a lot!
So there's no submissions made in year 2013.5? XD
Actually, I think Topcoder and Codecheff and codeforces are very good site for programmers and are similar but codeforces is easier to work in it .
codeforces results in 2014 was amazing but my results in 2014 ... ohm.
I think two things still can be improved in new year on Codeforces:
More comprehensive and in details editorials (like Topcoder's editorials). Maybe it should be one of the new year's resolution for authors of contests!
More categorized blog posts.There are many tutorial and interesting problems in specific category, in blog posts, but it's hard to find them.I think there should be some sorts of classification on some blog posts rather than tags.
I prefer if it's more div1 contests instead
Wow, better and better. CF has gained its popularity. Hoping to see more and more new features in CF:)
How long will the final testing take? was the only question for me when I saw the number of registrations.
I wish we see progress in judging process in 2015 :)
I am used to participating in other contests, where you have to wait few days for final results; waiting an hour for results of CF round isn't so bad. I agree even for slower testing after rounds, if we'll have stable working CF during rounds instead:)
this we are expected from the best online judge codeforces :D :D
Maybe this comment is the first record of 2015
I think the number of registered users in codeforces also include many fake registrants.
lool
looool
I think it is time to change this
Codeforces (c) Copyright 2010-"2014" Mike Mirzayanov
to
Codeforces (c) Copyright 2010-"2015" Mike Mirzayanov
It's time to find function that prints current year. It's 2015 now :)