Adobe Tells Me That My Code Sucks!

Posted At : April 16, 2008 11:38 AM | Posted By : Leif Wells
Related Categories: Flex, Adobe, Actionscript 3.0

Ah, bad habits. We all have them. In our lives and in our code. We let things slide. We don't clean up after ourselves. We assume that things are correct just because they work.

Well, not any more. Thanks to the heads up from Adrian Parr (I hate you for this, Adrian! I could have remained ignorantly blissful), Adobe has put us all on notice; Adobe has finally published Flex SDK coding conventions and best practices as part of their Open Source Flex initiative. I say "finally" because I believe that this is the very first time the mothership has begun setting some standards and coding Flex. Sure, there have been conference sessions and blog posts about this subject, but not this in-depth nor as specific.

Reading through the first few screens of this unfinished document I am already seeing things that I am doing incorrectly, according to this guide. Although I am quite certain that this guide is intended to standardize coding expectations for developers contributing to the Flex SDK, I am planning to begin following Adobe's advice more ridgedly in my own code in the future. In fact, I am recommending that this document be part of a guide for standard practices at my workplace. It makes a lot sense for me to make this recommendation because, ultimately, this guide is geared towards making it possible for large groups to code by one standard.

My worst habit? See the section labeled "Miscellaneous nomenclature." Ugh.

Which bad habits do you hate seeing from your team's code?