A while back, I think it was Ryan Matsikas (I hope I spelled his
surname right) that said something really profound and which I try to
apply to every Flash project I work on:
Mattes, thanks... ;-)
It's really not that profound, it's just that when all you have is a
hammer, everything starts to look like a nail. Just use the right tool for
the job. That includes not trying to make Flash do things that it doesn't do
well, especially when there are alternatives that do a much better job. And
keep in mind that the job of software development is 80% planning and 20%
writing code. If you plan well, you will write less code that is more
efficient, not to mention easier to modify and maintain. To be perfectly
honest, though, best practices really depend on the specifics of your
situation. In some companies, writing efficient, stable, and well documented
code is far more important than the deadline or the budget, while at other
companies the opposite will be true. Your best practices will depend heavily
on your employer's priorities, and the team (or lack therof) that you have
to work with.
ryanm
_______________________________________________
Flashcoders mailing list
Flashcoders@chattyfig.figleaf.com
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
