I was talking with my boss tonite about a big project coming up. He was explaining that a client was thinking of building a new site in AS2. I was dismayed. After developing with AS3 for a while, I was doing some AS2 work and hating it. After AS1, AS2 was a godsend, but after AS3, AS2 is a huge pain in the ass.
He patiently explained to me that my personal likings were not the only factors to consider. There was a lot of AS2 code that could be re-used. AS3 developers were rare and expensive, and training takes time. Etc.
In truth, weighing all these factors is above my pay grade. He is probably right in this case. But, of course, that’s not what I said. Instead, I threw out that AS3 development is just faster.
More… »
Posted by matt at 5:04 pm on October 16th, 2007.
Categories: code, office, workflow.
Last week I had my first freelance Flash gig, and it was more educational than I expected–or wanted–it to be…
The fault lie entirely on my side. The mission specs were vague and the timetable insane, but I understood that going in…and ultimately failed to adapt.
As a Flash hobbyist and learner, I've developed a consistent work process: ponder, plan, execute. Under the pressure and excitement of my first gig, I threw this process out.
This was a mistake. In the context of this particular gig, whether this process is optimal or not just doesn't matter, because it's my current process, and I can't swap it out for a new one with the ease of Keanu Reeves learning kung-fu in the Matrix.
The trick will be to adapt my current process to the task at hand. I should treat my work habits like components, throwing them into projects and parameterizing them accordingly, rather than trying to revamp habits, a longer-term undertaking.
Now I know.
Posted by pet-theory at 1:08 am on June 22nd, 2006.
Categories: office, workflow.
