Before I begin, let me first state the standard boilerplate of not speaking for my employer in any way and things discussed here are in no way an example of a future application or service. For that matter, nothing in here even happened. Ok, that's out of the way.
You are sitting in your office today, doing your usual work when your boss comes in and asks you when the college football bowls start. You check the usual suspects of sports sites and find out they start on the 20th of December, roughly 4 weeks away from today. Your boss leaves without explaining why and you don't think more about it until he comes back with that gleam in his eye that managers get when more work is coming your way.
His idea is to have a little contest for anyone who wants to sign up, to pick the winners of all the bowl games. Also, for the four BCS games, users choose the score of the games. There should be a way for the user to track their score as well as see the top scorers.
You start counting backwards from December 20th and your blood pressure raises. You don't have much time from design to implementation to testing to production so you make some quick decisions to get you started. The code will be written using Rails and the database will be MySQL.
The next step will be a quick design overview to make sure the initial pieces are there. That will be the next post.
Technorati Tags:
bowledover, rails