10 Things Every Senior Flash Developer Should Know

I interviewed several Flash / Flex developers as potential Roundarch employees. For me, the most difficult part of the interview was to understand exactly what questions to ask in order to assess the level of the Flash developer. Therefore, I created this list. This list allows me to assess the level and experience of the developer I am interviewing.

If you have not reached the level of "Senior-developer", then read the list and study the information on the links from it. If you find this list obsolete, please criticize it and tell about other links in the comments.


1. “The Elastic Racetrack” (The Elastic Racetrack)
You need to understand when events occur, when the code is executed and when the image is updated in Flash Player. This is really the basics of flash player.
www.craftymind.com/2008/04/18/updated-elastic-racetrack-for-flash-9-and-avm2
')
2. FlexSDK, mxmlc, compc, etc. (and all that jazz)
You need to understand what happens when you click the “run” button in Eclipse.
www.senocular.com/flash/tutorials/as3withmxmlc
livedocs.adobe.com/flex/3/html/help.html?content=apparch_08.html

3. Player events, user events, event ascents
I can not imagine what would be a Flash Player, without frames and mouse clicks.
www.adobe.com/devnet/actionscript/articles/event_handling_as3_03.html
livedocs.adobe.com/flex/3/langref/flash/events/package-detail.html
www.tink.ws/blog/custom-events-in-as-30-dont-forget-to-override-the-clone-method
jacwright.com/blog/70/how-to-listen-to-flash-events-that-dont-bubble

4. Operators, keywords and directives
You should not be surprised at the “new words” in AS3. If you don't know what “static” or “override” is or something else, then study this.
help.adobe.com/en_US/FlashPlatform/reference/actionscript/3/statements.html

5. ASDoc
Someday, one day, you will re-read your code and you will not understand what it means. This can be avoided if you properly comment on your code, but also do not forget that based on ASDoc generated cool documentation.
livedocs.adobe.com/flex/3/html/help.html?content=asdoc_3.html

6. Visual data management (images, fonts, CSS, etc.)
Flash is, first of all, a visual environment, so you need to know how to manage visual data with code.
www.gskinner.com/talks/flexlovesflash
code.google.com/p/queueloader-as3
code.google.com/p/bulk-loader

7. Arrays, Collections, Dictionaries, Mapping
You do not work with only one MovieClip, so you need to know how to control multiple objects as one object.
livedocs.adobe.com/flash/9.0/ActionScriptLangRefV3/Array.html
www.gskinner.com/blog/archives/2006/07/as3_dictionary.html
code.google.com/p/as3ds

8. Software animation (tweening, easing)
If you want things to remain still, then you should stay with HTML.
blog.greensock.com/tweenmaxas3
www.amazon.com/Foundation-Actionscript-3-0-Animation-Making/dp/1590597915/ref=sr_1_1?ie=UTF8&s=books&qid=1243014431&sr=8-1

9. OOP and the use of frameworks
The days of one big .as file are over. You need to be able to correctly place your code in organized objects suitable for reuse.
www.adobe.com/devnet/actionscript/articles/oop_as3.html
www.actionscript.org/resources/articles/684/1/Object-Oriented-Programming-in-AS3/Page1.html

10. Version Control
If you think that your code is worthless, you need to learn how to return value to it (??? I think that in the original post it meant that if you don’t use programs to control versions of the code, then you don’t appreciate your code and you need to learn to appreciate it using version control software).
User bkonst corrected me, and in my opinion suggested a more correct translation: if you do not think that your code is useless, learn how to store it correctly.
tortoisesvn.net/downloads
versionsapp.com
en.wikipedia.org/wiki/Revision_control
git-scm.com
www.nongnu.org/cvs

PS:
The original post is here: johnlindquist.com/2009/08/28/10-things-every-senior-flash-developer-should-know