So I’ve got a pretty good handle on ActionScript 3, I can make stuff that’s pretty and functional. I’d link to it, but then you’d all know where I work, not that you couldn’t find out anyway, as well, that link could be tracked, but I do the Analytics… Regardless, I would give up the barest of veneers between me and my work, and that would make me feel vulnerable and unable to post freely regarding the inadequacies of any management situation I might be experiencing. Not to say I am.
Instead, I offer you these lessons I’ve learned from OOP with ActionScript 3….
1) It never works the way you want the first time.
2) Most times fixing problems is a matter of looking at it from a different perspective.
3) Other times, you have to solve the situation, and the problem will fix itself.
4) Utilize experience when forming your plans, otherwise it’s no different than being intuitive in the moment.
5) A balance of stuff vs clutter enables functionality without getting overwhelmed.
6) Using standard naming conventions makes it easy to talk with others.
7) When it’s not working right, but no errors are apparent, your logic is faulty.
8) Cutting classes are not the answer, ensuring material in your classes overlap is.
9) Without taking notes along the way, it’s difficult to remember what you were thinking.
10) Someone else has likely traveled the same path before you, find them and ask questions.
And finally,
11) When faced with uncertainty, turn to the documentation.
