It seems that recently people, good people, are coming out of the woodwork to point out that they might not always like to deliver their Flash Platform solutions as OO solutions. I hear the collective gasp of horror and revilement from the community of Actionscript developers who have spent years refining their coding and OO methodologies to a point where they can code in Java with little effort. I myself am one of those coders. However, I am forever using the term â€˜Pragmaticâ€™ when I speak to staff and peers alike. Look at the big picture. Not everyone wants a solution that takes 2 months to deliver because you have to develop redundant, reusable, unit tested OO code. Many clients want throw away solutions and have no likelihood of code reuse.
We lecture on good process endlessly, but one of the initial stumbling blocks we have is that the right people don’t know what the term ‘process’ encapsulates, or they interpret a different or incomplete meaning to the word. So, what is process and more importantly, what is good process?