We offer a 4-year PhD position on Multi-Core Model Checking. This is a great opportunity to cut your teeth on multi-core software, in two ways:

• You get to do research on cutting-edge multi-core algorithms. Find new (parallel) ways to solve problems as efficient as possible on today's and near-future hardware.
• Find new ways how to prove multi-core algorithms correct (and apply them on in practice).

Either way, we have a stack of nice hardware ready, waiting to be exercized.

Deadline is November 1st, 2008! So, get your CV into shape and apply!

UPDATE 2008-10-20: Linked!

I collected some notes on collaborating in a small team using Git. These are mainly for the benefit of myself and my colleagues, but I would like to hear how others are using Git in similar situations.

I am becoming increasingly frustrated by Common Lisp's age. On the one hand, history makes it what it is: Mature, well-documented, thoroughly understood and practical. On the other, it fails to keep up with current system designs, lacking convenient native support for rich data structures, infrastructure access and parallel programming.

That reminded me of a paper by Richard C. Waters: The Survival of Lisp: Either We Share, Or It Dies (local copy), written in 1994. Here are some excerpts:

Unfortunately, the computer world around Lisp is changing so rapidly that considerable effort is required just to maintain links to the outside things that are essential, let alone all the things that are valuable.

If a programming language is little used in a given area, then there will be little reusable software written in that language, and little motivation for new programmers to start using the language in that area, which means that the reusable software in the language that does exist is unlikely to be properly maintained, which leads to even less interest in the language, etc. In contrast, if there is a critical mass of reusable software written in a given language in a particular area, then lots of programmers will be attracted to using this language in the area, which leads to an increase in the amount of reusable software, which attracts even more users, etc.

... which reminds me that I should probably dust off some code and bring it into a releasable state.