Skip to main content

Facebook app development

FB is cool. So better have an app for OSAC or iCode on Fb. May be something like SPOJ or codechef.com can have FB apps where signed up users could compete against each other.
What I mean is that, say there are 2 users user1 and user2, then user1 should be able to challenge user2 on some particular programming problem. If user2 agrees, then they both get to code, the judging is done ny our code. And all this activity is published on their FB stream .
like "user1 challenged user2 on problemno.2"
"user2 accepted the challenge"
"user1 scores 100 and user2 scores 200, hence user2 wins"
We can have something like this for solutions also.
like google code jam. 100 coding problems would be released on a particular date. Each problem has with it, 2 input files and one sample output file. one of the two inputs is a small one, of which corresponding output file is also provided.
what is expected out of the user is that he should code the solution , then test his solution with the input file we have provided and match his output with the output file that is also provided. once he is convinced that his code is producing valid results, then use the second BIG input file to produce a BIG output.
And then send this OUTPUT file as his solution to the problem.
we expect no code, but the output file. We will compare the output with the standard output file that's there with us. If matched, he is accepted as winner, else truncated.

Comments

Popular posts from this blog

सूनापन

मुद्दत हो गयी उन तन्हायियो को गुजरे , फिर भी इन आँखों में नमी क्यों है  ? तोड़ दिया मोहब्बत पर से यकीन मेरा, फिर भी मेरी दुनिया में तेरी कमी क्यों है ? हसरत है क्यों आज भी तेरी चाहत की मुझे, क्यों याद तेरी जेहेन से मिटती नहीं ? जलजला क्यों उमड़ता है ख्वाबो में मेरे, उस आशिकी की आगज़नी क्यों है  ? सन्नाटो में भी क्यों सुनता हू तुझे मेरी परछाई से क्यों तू जाती नहीं ? इन डबडबाती आँखों को तलाश तेरी, आज भी कहीं क्यों है   ?

How the Python import system works

How the Python import system works From:  https://tenthousandmeters.com/blog/python-behind-the-scenes-11-how-the-python-import-system-works/ If you ask me to name the most misunderstood aspect of Python, I will answer without a second thought: the Python import system. Just remember how many times you used relative imports and got something like  ImportError: attempted relative import with no known parent package ; or tried to figure out how to structure a project so that all the imports work correctly; or hacked  sys.path  when you couldn't find a better solution. Every Python programmer experienced something like this, and popular StackOverflow questions, such us  Importing files from different folder  (1822 votes),  Relative imports in Python 3  (1064 votes) and  Relative imports for the billionth time  (993 votes), are a good indicator of that. The Python import system doesn't just seem complicated – it is complicated. So even though...

What does it mean to “shift testing left”?

What does it mean to “shift testing left”? I used to think shifting left meant starting all these testing activities earlier in the process, but I realise it is more than that: it means  doing different things . Shifting left on testing means thinking about architecture and design differently, considering different stakeholders early and continually. Which in turn means shifting left on security, accessibility, and all the other dimensions of quality that we should care about. So shifting left on testing motivates all kinds of assurance activities, which can stop us over-investing in a solution that was never going to work. It is like TDD on steroids. As an unintended consequence, we can remove much of the traditional work that testers would have to do downstream when they only have late sight of the product. Again, we aren’t doing that work earlier, we are setting ourselves up to never need it at all!