Well, this would be my first blog post and I cant find a better event to start with than today's match.
I began the match thinking i'd regain my yellow spot and things seemed ok with problem A.
However, after a very quick submit on A, I had a pop up on my browser saying "Problem edited!". I instantly realised that i'd fail and made a quick resubmit. Lucky enough to have not locked it :D ! Sometimes, laziness helps :P !
I ended up starting B pretty slowly after reading the rather "long" statement twice atleast before I understood what it meant.After a good amount of coding and cooking up really "complicated" ideas for it, i made a submit. Just 30 minutes left for the contest to finish now! :|
One quick glance at the standings page told I were doing good till now. I went back to my room hacking solutions on edge cases in A.Lucky to have found 1 or 2 even after 2 hours into the contest.
10 minutes before the contest ending and guess what?? My solution to B gets hacked. I'm very sure about the idea and still its a "successful hacking attempt" :| !
After a treacherous 30 minutes of waiting, I register for practise and make a resubmit.
And undoubtedly so, I get "Accepted" :( !!
For the people, who've enthusiastically read till here, the bug i had in my code was rather funny and im sure the way i coded it made it easy for my challenger.
#define MAXL 100011
char s[MAXL]; // the word entered by user
//the above line is undoubtedly correct
char t[MAXL]; // a temporary array for holding the potential address
Although the last line seems ok at first glance, it fails with a runtime error on the judge for having misunderstood the problem statement.
Lesson Learnt: Being Careful is as much required in the contest as Coding Fast and Accurate! :(
All the best for the remaining matches, and wish you high new ratings! :)
Good day, folks!!
I began the match thinking i'd regain my yellow spot and things seemed ok with problem A.
However, after a very quick submit on A, I had a pop up on my browser saying "Problem edited!". I instantly realised that i'd fail and made a quick resubmit. Lucky enough to have not locked it :D ! Sometimes, laziness helps :P !
I ended up starting B pretty slowly after reading the rather "long" statement twice atleast before I understood what it meant.After a good amount of coding and cooking up really "complicated" ideas for it, i made a submit. Just 30 minutes left for the contest to finish now! :|
One quick glance at the standings page told I were doing good till now. I went back to my room hacking solutions on edge cases in A.Lucky to have found 1 or 2 even after 2 hours into the contest.
10 minutes before the contest ending and guess what?? My solution to B gets hacked. I'm very sure about the idea and still its a "successful hacking attempt" :| !
After a treacherous 30 minutes of waiting, I register for practise and make a resubmit.
And undoubtedly so, I get "Accepted" :( !!
For the people, who've enthusiastically read till here, the bug i had in my code was rather funny and im sure the way i coded it made it easy for my challenger.
#define MAXL 100011
char s[MAXL]; // the word entered by user
//the above line is undoubtedly correct
char t[MAXL]; // a temporary array for holding the potential address
Although the last line seems ok at first glance, it fails with a runtime error on the judge for having misunderstood the problem statement.
Lesson Learnt: Being Careful is as much required in the contest as Coding Fast and Accurate! :(
All the best for the remaining matches, and wish you high new ratings! :)
Good day, folks!!
All the more reason for writing the blog post so that people would understand my plight better :) .
Hoping both of us don't do it again i guess :P .
At a quick glance, it seemed computational geometry.
Fingers crossed for the srm today.
Ciao! :)