## Monday, May 13, 2013

### Joel Spolsky in Krakow

Friends,

We would like to share a real goodie with you (especially the ones in or close enough to Poland this week): Hive53 - a community of startup and entrepreneurship enthusiasts making Krakow brim with energy and KGD host Joel Spolsky this Friday, May 17th in Krakow.

Joel is co-founder and CEO of Stack ExchangeFog Creek Software and has inspired a great many of us with his insights (www.joelonsoftware.com) into how to make software start-ups rock. In Krakow he will be 'live', hence if you are in the region, join in and enjoy!

Event details here

We, Natalia and probably Dominic from Codility, will be there too. Hence, look us up if you feel like a common drink. :)

## Friday, May 10, 2013

We're hungry for great new team mates.

Check out http://codility.com/jobs/.

## Tuesday, May 7, 2013

### New challenge is online: Hydrogenium 2013

A new Codility challenge is online: Hydrogenium

Feel up for the Challenge: Then turn to http://codility.com/cert/start/hydrogenium2013/, code and see whether you can hit gold level.

If you want to train a little before, hit our http://codility.com/train/ site.

Have fun, good luck and spread the word if you got the certificate!

## Monday, April 29, 2013

### Train yourself!

In response to requests made by many fans of Codility certificates we have collected all the previous challenges and solutions in one place. Hit codility.com/train and train yourself, for free.

This is just a start and we aim at building the training centre from here. More programming tasks and challenges to come. Any requests or ideas in this respect?

Happy training!

## Tuesday, April 23, 2013

### Codility now also hacks ice cream

.. well not exactly a new business line of Codility, but then, one's got to have fun and indulge in other nice sides of life at times, right?

Stay tuned for the opening bash ouf our new office space (ETA end of June), be in WAW and join us to savor version 2.0 then!

@Sumo Logic: We are seriously impressed with the sturdiness of your products! .. blame our co-worker Jacek Migdał for making us play with it.. :) greetings to Mountain View!
@Lickmeimdelicious.com: Apologies for (ab)using your awesome logo. But then, we know you are the real deal in nitro ice cream!

## Friday, April 19, 2013

### Psi 2012 Codility Programming Certificate Solution

After a break, we are returning to our monthly Codility Certificates. This time we will see how the Ψ (Psi) certificate can be solved. You can still give it a try, but no certificate will be granted.

In this task, there is a grid of wires through which an electric current flows between the lower-left and upper-right corners. The wires burn out sequentially in some order. The question is: how many wires must burn out to cause the current to stop flowing?

Checking whether the two corners are connected is a standard graph problem, and there are standard algorithms for checking graph connectivity: for example, DFS and BFS. Each of them requires $$O(N^2)$$ time, where $$N$$ is the size of the grid. But there are up to $$2N(N−1)$$ wires that can burn out, and equally as many moments at which we should check whether the two corners are still connected. So the overall time complexity of such a naive solution is $$O(N^4)$$. Here is an implementation of such a solution in Python:

def check_connections(horizontal, vertical):
N = len (horizontal)
visited = [[False] * N for j in xrange(N)]

def dfs(i, j):
if (not visited[i][j]):
visited[i][j] = True
if vertical[i][j]:
dfs(i, j+1)
if horizontal[i][j]:
dfs(i+1, j)
if (i > 0 and horizontal[i-1][j]):
dfs(i-1, j)
if (j > 0 and vertical[i][j-1]):
dfs(i, j-1)

dfs(0, 0)
return visited[N-1][N-1]

def wire_burnouts(N, A, B, C):
vertical   = [[True] * N for j in xrange(N)]
horizontal = [[True] * N for j in xrange(N)]
for i in xrange(N):
vertical[i][N-1]   = False
horizontal[N-1][i] = False
for t in xrange(len(A)):
if C[t] == 0:
vertical[A[t]][B[t]] = False
else:
horizontal[A[t]][B[t]] = False
if not check_connections(horizontal, vertical):
return t+1
return -1


Unfortunately, such a solution fails on larger tests due to stack overflow. Also, there are faster solutions.

Firstly, we don’t have to check all possible moments in time: once the current stops flowing it never starts flowing again. Hence, we can use a bisection to find the moment when the current stops flowing. Bisection requires us to check connectivity at $$O(\log N)$$ different moments in time, and each such check takes $$O(N^2)$$ time, so the overall time complexity is $$O(N^2 \log N)$$ time.

Secondly, instead of using recursion, we can implement DFS using an explicit stack.

def check_connections(horizontal, vertical):
N = len (horizontal)
visited = [[False] * N for j in xrange(N)]
stack = [(0,0)] * (2 * N * N)
sp = 1

while sp > 0:
sp -= 1
(i,j) = stack[sp]
if (not visited[i][j]):
visited[i][j] = True
if vertical[i][j]:
stack[sp] = (i,j+1)
sp += 1
if horizontal[i][j]:
stack[sp] = (i+1,j)
sp += 1
if (i > 0 and horizontal[i-1][j]):
stack[sp] = (i-1,j)
sp += 1
if (j > 0 and vertical[i][j-1]):
stack[sp] = (i,j-1)
sp += 1

return visited[N-1][N-1]

def wire_burnouts(N, A, B, C):

def burn_wires(t):
horizontal = [[True] * N for j in xrange(N)]
vertical   = [[True] * N for j in xrange(N)]
for i in xrange(N):
vertical[i][N-1]   = False
horizontal[N-1][i] = False
for i in xrange(t):
if C[i] == 0:
vertical[A[i]][B[i]] = False
else:
horizontal[A[i]][B[i]] = False
return check_connections(horizontal, vertical)

def bisection(l, p):
# Search for the first moment without a connection
if l == p:
burn_wires(p)
if burn_wires(p):
return -1
else:
return l
else:
m = (l+p)/2
if burn_wires(m):
return bisection(m+1, p)
else:
return bisection(l, m)

return bisection(0, len(A))

Even so, this is still not the best possible solution. Instead of burning the wires out, we can reverse time, keep adding missing wires and check when the two corners are connected. For this approach the best data structure to use is a find–union tree. This is suitable for storing information about a set of elements (nodes of the grid) grouped into disjoint subsets (here, connected components). Using find–union trees, we can quickly check whether two elements are connected (find) or add a new wire (union). The amortized time cost of operations on such trees is $$O(\log^*N)$$. ($$\log^*$$ is the iterated logarithm, the number of times one has to iterate the $$\log_2$$ function in order to obtain a number not greater than 1. In practice, its value doesn’t exceed 5 and can be treated as constant.) Hence, the overall time complexity of the solution is $$O(N^2\log^*N)$$.

Here is an implementation of such a solution:

def find((a,b)):
global vertices, rank

(c,d) = (a,b)
while vertices[a][b] != (a,b):
(a,b) = vertices[a][b]
while vertices[c][d] != (a,b):
(e,f) = vertices[c][d]
vertices[c][d] = (a,b)
(c,d) = (e,f)
return (a,b)

def union((a,b), (c,d)):
global vertices, rank
(a,b) = find((a,b))
(c,d) = find((c,d))
if rank[a][b] < rank[c][d]:
vertices[a][b] = vertices[c][d]
else:
vertices[c][d] = vertices[a][b]
if rank[a][b] == rank[c][d]:
rank[c][d] += 1

def wire_burnouts(N, A, B, C):
global vertices, rank
M = len(A)

# Find-union data-structure
vertices = [[(x,y) for y in xrange(N)] for x in xrange(N)]
rank = [[0] * N] * N

# Edges left at the end
v_edges = [[True for y in xrange(N-1)] for x in xrange(N)]
h_edges = [[True for y in xrange(N)] for x in xrange(N-1)]
for i in xrange(M):
if C[i] == 0:
v_edges[A[i]][B[i]] = False
else:
h_edges[A[i]][B[i]] = False

# Merge vertices connected at the end
for i in xrange(N):
for j in xrange(N):
if i < N-1 and h_edges[i][j]:
union((i,j), (i+1,j))
if j < N-1 and v_edges[i][j]:
union((i,j), (i,j+1))

if find((0,0)) == find((N-1,N-1)):
return -1

# Simulate wires burning out, in a reversed order
for i in xrange(M-1, -1, -1):
if C[i] == 0:
union((A[i],B[i]), (A[i],B[i]+1))
else:
union((A[i],B[i]), (A[i]+1,B[i]))
if find((0,0)) == find((N-1,N-1)):
return i+1


## Friday, January 11, 2013

### Codility Certificate Challenge – Yearly Summary 2012

It has been an extremely intensive year for Codility. Our Certificate Challenge Program has become more and more popular, depriving both Marcin Kubica and our Support Team of their beauty sleep! We’ve had great fun with it, and we hope that you have too!

### For your interest, here are some statistics from 2012:

1. We have published 10 Certificates

2. We have awarded 838 Gold and 2590 Silver Certificates

3. We have received 118 388 submissions

4. The Champion tried to solve one Certificate 68 times (congratulations – Gold was finally achieved!)

5. The most popular language was Java

6. The most Gold Certificates were achieved in C++

7. We have awarded just 1 Gold in VB.NET and in Objective-C

8. No Certificates have been awarded in Lua or Pascal

8. Among the Silver certificates, the most poplar languages were Java and C#

Thank you all for your efforts this year, and have fun in the coming months! The first Certificate Challenge of 2013 now awaits you!

And by the way… we're hiring! If you are passionate about Codility, drop as an email at jobs[at]codility.com.