Setting up a team...
revolutionary.dan at gmail.com
Fri Mar 24 17:11:37 EST 2006
While I concur that going with an experienced Rev developer as a consultant
is probably the best way to approach this problem/opportunity, I'd suggest
you may need two consultants or a well-coordinated team. Because you really
want, as an end result, an internal team with a good foundational
understanding of Rev. That means you need someone to train one or more of
your team members. It's a rare bird who can both consult and teach/train but
technology transer here feels more important than specific near-term project
completion. If I'm right about that, then I'd bring in a trainer.
On 3/24/06, Thomas McGrath III <3mcgrath at adelphia.net> wrote:
> Hire an experienced Revolution Consultant and then program it
> yourself and introduce your team to it in progress. Then you have
> control over the project instead of someone new to REV who will
> probably try to fit Rev into their thinking instead of their thinking
> into Rev. Secondly, the consultant can teach and inform and consult
> on the best practices and usage during the planing stage and if you
> get into trouble they are already familiar with the project and can
> step in to help in the actual programming.
> You team will take the consultants lead and our lead and in the end
> get a great intro to Rev and it's paradigm.
> Sounds like a win win to me.
> Good luck and as someone on this list told me "Go for it, Just jump
> in and start"
> On Mar 24, 2006, at 11:47 AM, Stephen Barncard wrote:
> > Rev is natural to me...But I've been xtalking since 1988.
> > My gut says hire a rev-experienced person first so management can
> > see the thing work sooner. Quicker results = success
> > sqb
> >> At the moment we do websites and that's it. However, we've
> >> recently been
> >> bidding for bigger and bigger jobs that although the customer
> >> thinks "hey,
> >> that'd be cool on a browser", I think that their users (internal
> >> that is)
> >> would feel far happier with a client application. So, as the Tech
> >> director
> >> of the company, it's my job to source the best method of doing
> >> these things.
> >> Now, I got RunRev as a hobby thing. I like programming and I like the
> >> challenge of new stuff, and this seemed a good toy to take me away
> >> from the
> >> humdrum of office life (busman's holiday I know, but us geeks are
> >> like
> >> that). However while I'm sat in a meeting the other day listening
> >> to some
> >> requirements, it hit me like a bolt that RunRev could do all and
> >> more of
> >> what was required.
> >> So, totally hypothetical at the moment, but let's say we decided
> >> to write
> >> some stuff in RunRev. We've got a small dev team of three PHP
> >> programmers
> >> and although they may find it fun, we really don't want them to
> >> take their
> >> eye off the ball. So I have a dilemma. Do I go looking for a RunRev
> >> programmer, do I freelance our requirements or do I take someone
> >> on and
> >> train them in the art of Transcript?
> >> Open discussion really, what would you do?
> >> Andy.
> > --
> > stephen barncard
> > s a n f r a n c i s c o
> > - - - - - - - - - - - -
> > _______________________________________________
> > use-revolution mailing list
> > use-revolution at lists.runrev.com
> > Please visit this url to subscribe, unsubscribe and manage your
> > subscription preferences:
> > http://lists.runrev.com/mailman/listinfo/use-revolution
> Thomas J McGrath III
> 3mcgrath at adelphia.net
> Lazy River Software™ - http://www.lazyriversoftware.com
> Lazy River Metal Art™ - http://www.lazyriversoftware.com/metal.html
> Meeting Wear™ - http://www.cafepress.com/meetingwear
> Semantic Compaction Systems - http://www.minspeak.com
> SCIconics, LLC - http://www.sciconics.com/sciindex.html
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
Dan Shafer, Information Product Consultant and Author
Get my book, "Revolution: Software at the Speed of Thought"
More information about the Use-livecode