On 4 Jul 2013, at 13:08, Sean Bamforth <[email protected]> wrote: > The current development environment is such that newer features are either > very slow or impossible to develop.
This bears repeating: it's more important to understand why this is the case than to solve the problem this time round. Even if rewriting the app buys you some productivity in the short term, Rails has its own tar pits. Without improving the client's mental model of software development, if you go down this route, I predict you'll be back here in a few years asking how to rewrite their legacy Rails app because it's slow or impossible to develop against. I'd wager a bar tab at NWRUG on it. Matt Wynne's experience is relevant here[1]: "A few months ago, development of http://relishapp.com reached what is a familiar but rather unpleasant plateau for me. … Unfortunately, the very forces that make adding features to a new Rails application so easy are the same ones that start to hold you back as the number of features grows." In fact at Scottish Ruby Conference 2012 he teamed up with Steve Tooke and a certain Kevin whose name you might recognise to talk about this[2]. (That talk is surprisingly hard to track down it seems.) To re-iterate what others have said: you'll be better finding someone with this level of experience to offer another perspective before committing to any major development projects. Ash [1] http://blog.mattwynne.net/2012/04/09/hexagonal-rails-introduction/ [2] http://vimeo.com/55733029 -- http://www.patchspace.co.uk/ http://www.linkedin.com/in/ashmoran -- You received this message because you are subscribed to the Google Groups "NWRUG" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/nwrug-members. For more options, visit https://groups.google.com/groups/opt_out.
