thinking out loud [...]by @robertodecurnex


Finally the very first Rally on Rails contest has opened its registration. As some of you may know this is the Latin American version of the Rails Rumble and, following the same concept, the registered teams will be trying to write a productive Rack base web application, from scratch, in just 48 hours.

There was no more time to loose, I had to gather the team and start working on the main concept of the application right away. Since I’m almost a solo developer right now I had to pick some of my old partners (now split all around Argentina).

@elgalu

A flexible developer with expertise in a wide range of technologies. He is a strong Rails + JS developer, currently focused on Automation. Although he performs very well with CSS he is not the happier man ever when working with it. He also owns this huge collection of tip notes, it’s like a walking human-like StackOverflow.

@jmoren_06

The practical guy. He is the only one who is really creating stuff that works on this world full of mortal souls. He is mainly focused on the creation of business dedicated applications with rich user interfaces. He is also the team philosopher and a big open source enthusiastic.

???

There is this other guy, a great friend of mine, but, until now, he is not ready to be committed to the project. He still have a whole week to think about it (until the end of the registration period).

So it’s time to start working! Base on the contest rules there are a lot of things that we can start with. This week main objectives will include long hours of discussions about the project scope and the creation of an initial list of potential tools to be used. The latter one is really important since we all need to have a medium+ level of understanding of them in order to prevent unnecessary time looses during the contest period.

Hopefully on the next week’s progress report I will be able to share with you some deeper details about what’s going on.

Are you ready to race against us?

blog comments powered by Disqus