David Kramer's high-entropy blog

Adobe Flex For Software Engineers

I have to admit when I first experienced Adobe Flex, the successor to Adobe Flash for rich internet application development, I thought it was a fragile toy that wasn’t good for much more than pretty moving pictures.  At my current day job, I had to not only learn it, but spend about half my time working in it (as opposed to my current favorite language, Java).  One thing I’ve learned from the experience is that it wasn’t so much Flex that I had a problem with, as much as Flex Developers.  The Flex developers I’ve worked with up until this job came to Flex from being Illustrators, Graphic Artists, or just kinda fell into it.  They never learned the art of software development, never learned to appreciate best practices, and never learned to value code quality or readability.  But as a long-time Software Engineer, I know you can create bad software in any language.  But now I’ve spent about 10 months working in Flex, and feel I can opine fairly. Read on…


Site info