I do not question the design patterns but rather their misuse (effect paternity) see their poor comprehension.
While the problem of poor acquisition of bases and principles of OOP to discover patterns. Too many projects that do not take the road with this type of framework and I speak from experience (difficult to maintain, too many shortcuts are used by developers to circumvent the separation, etc. ...). Companies do not use these frameworks because they have had a bad experience and I do this by finding everyday on the ground. I have no ill feelings but rather I do not support that they laugh at people who allege they are the solution has it all. I regard my comprehension (bases, principles and patterns) and I check my code and my line of conduct architect meets my needs, that's all. Iteratif ++ PS: si je n'arrive pas a me faire comprendre, je l'ecris en français ;) _______________________________________________ osflash mailing list [email protected] http://osflash.org/mailman/listinfo/osflash_osflash.org
