>>So I, as a developer, either have to change the design bits to fit >>into the Rails conventions or try to live with the design as-is.
Others have replied about the importance of being involved in the "process" and I totally agree with them. HOWEVER, one thing I feel strongly about is the suggestion "change the design bits to fit into the Rails conventions" I see my job as helping the Customer deliver, not changing the Customers expectations to fit what I or some framework can or can't do. Communicating with the rest of the team on the "cost" of taking one approach verses another is also my job but in the end it is the Customers choice not mine on which approach is taken and how the design is or isn't. When Steve Jobs says I think tablet computers are the way to go, how do you think he would react when the engineers say "but Mr Jobs, desktops are all we can build?" See the Design as a challenge and learn new ways of delivering it or get a framework/language that does, but don't try to change them. Suggest the pro's and con's of each approach and let the Customer decide. Rgs, James. -- You received this message because you are subscribed to the Google Groups "Ruby or Rails Oceania" 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/rails-oceania?hl=en.
