Competition languages stats

Python wins competitions! (1/3)

Python wins competitions! (2/3)

Python wins competitions! (3/3)

Intro to Google Code Jam

https://code.google.com/codejam

Once per year, several on-line rounds a on-site round and $20k prizes

Solve three to five problems with known-correct solution

All programming language allowed:

     download input, run code on your computer, upload output

Competition is timeboxed to a few hours, code runtime to a few minutes

A small and a large input datasets with different scores

Ranking by problem score and submission time

Problem definition anatomy

Problem statement:

    problem universe with actors, parametric rules and a question

Limits:

    range for parameters and initial conditions for small and large inputs

Sample test cases:

    the set of parameters and initial conditions along with the solutions

Test cases:

    the set of parameters and initial conditions to solve

Problem solving anatomy

Constraints:

    CPUs, RAM, storage space

    code running time, wall-clock time

Coding phases:

    modeling

    coding

    performance-tuning (optional)

    debugging (optional)

    runtime

Solution analysis: "simple solvable" problem

Constraints:

    CPUs, RAM, storage space

    code running time, wall-clock time

Coding phases:

    modelling: 2m

    coding: 2m

    performance-tuning: 0

    debugging: 1m

    runtime: 1m

"Generalised solvable" problem

Constraints:

    CPUs, RAM, storage space

    code running time, wall-clock time

Coding phases:

    modelling: 2m ⎯ 20m

    coding: 2m ⎯ 20m

    performance-tuning: 0 ⎯ 20m (PyPy beats CPython)

    debugging: 1m ⎯ 60m

    runtime: 1m ⎯ 8m

"Simple unsolvable" problem

Constraints:

    CPUs, RAM, storage space

    code running time, wall-clock time

Coding phases:

    modelling: 20m ⎯ ∞

    coding: 2m ⎯ 20m

    performance-tuning: 0 ⎯ 20m

    debugging: 1m ⎯ ∞

    runtime: 1m ⎯ 8m

"Generalized unsolvable" problem

Constraints:

    CPUs, RAM, storage space

    code running time, wall-clock time

Coding phases:

    modelling: ∞

    coding: ∞

    performance-tuning: ∞

    debugging: ∞

    runtime: 4m ⎯ 8m

Strategic thinking

Wall-clock time is the paramount asset

    time management is the key

Problem selection

    go for simpler problems first

    go for simple (even brute force) solutions for small inputs first 

    keep an eye on the scoreboard

        check what the pros are doing

        address problems that can make you pass the round

Focus and stress management

Focus management:

    round strategy and problem strategy

    do not make mistakes while coding (KISS)

    be ready to question all your assumptions

Stress management:

    keep calm in the face of a ticking wall-clock

    keep calm in the face of the risk of public shaming

    never give up

How do I start or get better at competing?

How do I start or get better at competing?

Practice:

    practice real world competitions, from start to end. With a timer!

    go for volume first, solve a lot of "simple solvable" problems

    then go for "generalised solvable" problems

    learn from the code of other competitors

    learn to use libraries (networkx, pulp, gmpy2, scipy, etc.)

    build your library of custom code

Learn data structures and algorithms:

    "Learn To Think Like A Computer Scientist" by Tim Roughgarden

What do I learn for everyday programming?

Wall-clock time management:

    modelling: days

    coding: days

    performance-tuning: weeks

    debugging: weeks

Strategic thinking

    solve simpler problems first

    keep an eye on the scoreboard

Life, the universe and everything

Focus and stress management:

    a bug in production

    client-facing problem solving

    job interviews

    ...

    you are trapped in a fire!

Strategic thinking:

    wall-clock time management

    keep an eye on the scoreboard