I can attest to this.
Our app has been developent for well over a year, and in production
for about 10 months, yet no-one on the outisde has ever seen it.
Large companies have all kinds of business/competitive reasons for
releasing (or not as in our case) stuff to the outside world.
Also I can tell you that in our case, a typical (short) release cycle
lasts about 3 months, at least two of which is spent testing and about
3 weeks for development. We connect to so many complex back-end
systems that testing is very difficult. We have had about 4 releases
with Flex.
I think at any time we probably have 4 different environments with
stuff on the go at different stages and versions with development,
testing, staging, production. Everything is spread out over several
different geographical regions. Load balancers, hardware encryption
and tunneling, clusters for all of those. So obviously we have more
than one Flex license ;)
Freqequent changes in requirements is where Flex really shines. We
can make major changes on the Flex side in hours/days, whereas the
guys doing back-end systems often take days/weeks to do the equivalent
thing or whatever is needed to keep up with us.
Oops - I think I am beginning to sound like a salesman, but I thought
I would give a little view into my world.
Jonathan
On 5/20/05, David Mendels <[EMAIL PROTECTED]> wrote:
<snip>
> But many more are longer term projects. I am aware of many
> Flex customers with development teams that have a 6-18 month development
> and testing cycle for large and complex applications.
</snip>
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/flexcoders/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
