As we continue to transition from HTML/Javascript user interfaces to Flex ones here at work, we continue to go through the expecting growing pains when learning any new technology. From the simple (“How on earth do I specify a custom tooltip? oh…), to the complex (“If we provide the ability to move this control within the panel, how do we get the other controls to adjust themselves accordingly? oh….”), we’ve had many AHA! moments in the past few months.

Luckily, we are all very seasoned application developers, and there have only been a few problems to which we’ve been unable to apply past experiences and overcome quickly. Our expertise is growing quickly, and I can see in my head a year from now, after we’ve all built our collective intellectual base of knowledge of Actionscript and MXML, what amazing things we’ll be able to accomplish as we move beyond the mundane tasks of figuring out the intricacies of a ViewState, to being able to conceptualize the application as a whole and how it fits into the business needs.

It’s been amazing to see the difference at how quickly a new technology can be learned and implemented when working with a team of developers who are advanced and experienced , as opposed to a smart, talented novice.

It’s that vast accumulation of failures and successes and stored design patterns and workarounds that we all build during our careers that can significantly reduce the cost of a technology transition. I remember reading an article not long ago from someone espousing that experience – while definitely a factor – is not one of the major factors when looking to hire new developers. I’ve always disagreed with that. Someone with 10 or more years experience is likely able to learn technology faster, see hurdles ahead and how to avoid them, and generally see the big picture better than a greenhorn.

So the growing pains continue, but they hurt less and less each day.