This is a general question about workflow. For a long time I have been
working on Flash projects independently. Over time everything has gotten
bigger. Projects are now at a scale where I must collaborate with other
Flash programmers. I am looking for suggestions about best practices for
organizing and dividing up work on large Flash projects. What are
problems and solutions that people have encountered when sharing work?
I would just echo Aron's and Jester's posts, you're crossing a line and
moving from "website development" to "application development", and you'll
need to treat it that way. Likely the most difficult thing to convince your
higher-ups about will be the necessity of redundancy and planning. They seem
expensive at first glance, especially if they are used to telling you what
they want and seeing it show up on the production server a week later. But
as soon as you add other developers into the mix, planning ahead becomes
vital, and having a staging enviornment that is an exact duplicate of your
production enviornment is critical. And nothing should go to production
without regression testing. It will make things take longer, but not nearly
as long (or expensive) as putting bad or incompatible code out to production
and having to go troubleshoot it and fix it there.
And get familiar with your source control, it is a life saver.
ryanm
_______________________________________________
[email protected]
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com
