Strange Rails Project Ever


I am currently working in a company called Webtoday business and the first Rails project here  seems to be quiet strange. Right from the start the client seems to worry too much about database. In fact he wants to design databases first before doing a single line of Ruby code. What? I am quiet puzzled. Really puzzled.

Rails is meant to get you head start, its supposed to make programmers life breeze and if one wants project in Rails, he must respect programmers. Now I am updating huge excel sheets and arguing with client what possible columns should or should not be there, reading mini-novel sized technical emails. It all sucks.

To rub salt on wounds the management wants me to pass every email to it, we have a tech discussion before even sending a hello to client. My life is in ruin. I am running in and out of meetings and just waiting my time. So much time has been wasted, that if I alone had coded diligently would have finished the beta version of the product. God! I have given up hopes that this client would ever understand Rails and  would not be surprised if the project fails.


  1. Leave a comment

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: