About the Darwin Race of Languages

AND THE WINNER IS: WEREWOLF

The results of the voting are:

  1. Werewolf
  2. Jan Wicher
  3. Tom Glenn

The winners got to pick their own prizes from the products made available by our sponsors.

#1. Werewolf.

He picks SmartInspect as his prize.

#2. Jan Wicher.

He picks DevExpress VCL Subscription as his prize.

#3. Tom Glenn.

He picks the DataAbstract license as his prize.

What is this all about?

This contest is about gathering experiences from real developers working on the same problem in different IDEs and languages. At the end of the contest we can judge what platform gives the best result and helped the programmer best.

When developers discuss their favourite tools, things can get heated some times. Most of us are pretty sure that we are working with the best language and tool available out there. Anyone trying to tell us otherwise is wrong and we like to tell them quite fanatically so.

It was at such an occasion (on the web this time) that I wanted to try to get people make a case for their favourite language and IDE using experiences from a real life example. So I came up with this contest. If people from all camps implement a software solution with their favourite tool, and document their work, we can compare notes. We can use those solutions and experiences to see where languages and tools excel en where they are not so good.

What's to win?

At the moment there are three prizes to pick from. The winner picks the first prize, the runner up gets the other. If during the competition more sponsors come along, number three gets to pick a prize also. If a fourth sponsor comes alone, well, you must have worked out the algorithm by now.

Who can enter?

Every programmer, team of programmers, amateur or professional alike. Delphi, C#, C++, Java, Smalltalk, Assembler, Plone, Silverlight, Adobe/Air, and all other platforms and languages can be used to your liking. The end result isn't a good piece of software per se, but a list of true life experiences while programming.

There is no limit to using any component set or other tools that you see fit. It should be just like another little project that you are doing for real. But, remember, if you use a component set or tool, spend some time documenting on it.

  • There are three problems to pick from. Just pick the one that you think will make the best case for your favourite tool.
  • Every programmer will create an implementation and will keep records of their experiences doing so.
  • We'll schedule one 2 week sprint (we all do agile nowadays, don't we) and we'll stop after that.
  • You can spend as much time on it as you like or can afford to, just as long as you document your experiences and feelings working on it.
  • The results, software and the experiences, will be published on the web for all to see.

Contractors

There is a special note for contractors out there. This of course is a fine moment to show what you are made off for the whole world to see. You can show programming capabilities, communication skills, self criticism, et cetera. Those are all things that possible clients are most interested in. Making a case for your tool of choice is making a case for yourself. Your work, including your contact details, get published on this site.

But, most important of all: it's for fun and the outcome of the contest is another subject that we can argue about for some time.