Sorry, one last thing. Yes a developer should question the client's requirements, but to do that you need to earn their respect.
I can do COBOL so if I say that it would be better to implement things in a different way the client will consider it because they know that I know what I am talking about. But if I am just wanting to do things differently because language / technology X is not my favourite toy then the client will have no respect for me. Or if I am insisting that it can only be implemented with language / technology X simple because that is all I know the client will also have no respect for me. To earn respect you need to prove that you know what you are talking about, you need to show your skills. That means learning OSs, languages and technologies that you have no love for. Not merely learning enough to get by but mastering them. I have no love for Java, Cocoon, IIS, MSQLServer or Windows. But guess what! If that is what needs to be done I'm your man. Think of it like this, you ask the question "I have to set up a development environment for Rails on Windows. What advice can you give me?" Which answer do you think would make you respect the person you were talking to? 1) Ugh. Windows SUX. I hate it. You should get a Mac. 2) Well you could install Eclipse, there are some nice tools for Rails development. Here's a version of MySQL that integrates well with Windows, you should install that. Or perhaps you could try the Instant Rails package and Notepad++ if you don't like Eclipse. Or perhaps Netbeans would suit you better. To give answer two and to earn respect you need skill, which means experience. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
