Comments on: Flex Application View Organization http://blog.foomonger.com/2009/11/21/flex-application-view-organization/ Tips and Musings on Software Development, Flash, and Flex Fri, 03 Dec 2010 04:27:32 -0600 http://wordpress.org/?v=2.8.4 hourly 1 By: Sam Ahn http://blog.foomonger.com/2009/11/21/flex-application-view-organization/comment-page-1/#comment-37 Sam Ahn Wed, 02 Dec 2009 04:53:03 +0000 http://blog.foomonger.com/?p=45#comment-37 With good documentation and good communication I think there can be more reused code, but I think that effort would have to be done very very purposefully, i.e. clearly creating a component architecture, supporting docs, clean code organization. This reused code should probably even be in a separate code-base than the application code to further distinguish what is reused and how to maintain what. Personally I haven't seen this executed well very often which I think is the norm. If you have a "performing" team and the right project, then I think it can be more appropriate and successful. With good documentation and good communication I think there can be more reused code, but I think that effort would have to be done very very purposefully, i.e. clearly creating a component architecture, supporting docs, clean code organization. This reused code should probably even be in a separate code-base than the application code to further distinguish what is reused and how to maintain what. Personally I haven’t seen this executed well very often which I think is the norm. If you have a “performing” team and the right project, then I think it can be more appropriate and successful.

]]> By: Johnny Boursiquot http://blog.foomonger.com/2009/11/21/flex-application-view-organization/comment-page-1/#comment-36 Johnny Boursiquot Tue, 01 Dec 2009 15:59:51 +0000 http://blog.foomonger.com/?p=45#comment-36 I would agree that there is a distinction between application development and framework or component library development. In one you're trying to achieve a specific business goal and in the other you're providing tools for others to accomplish their business goals a little more easily. What I think is lacking in your argument is how to maximize re-usability. If each team member is creating similar components or writing similar classes with slight variations between them for the sake of maintainability, that seems almost like wasted effort to some degree. In many cases, maintainability is a laudable goal, but I'd like to think that there should be a better balance between maintainability and re-usability. Perhaps it is achieved through better communication between developers and better documentation of what's there and what changes need to be made to keep existing code working *and* extending them for new purposes. What do you think? I would agree that there is a distinction between application development and framework or component library development. In one you’re trying to achieve a specific business goal and in the other you’re providing tools for others to accomplish their business goals a little more easily.

What I think is lacking in your argument is how to maximize re-usability. If each team member is creating similar components or writing similar classes with slight variations between them for the sake of maintainability, that seems almost like wasted effort to some degree.

In many cases, maintainability is a laudable goal, but I’d like to think that there should be a better balance between maintainability and re-usability. Perhaps it is achieved through better communication between developers and better documentation of what’s there and what changes need to be made to keep existing code working *and* extending them for new purposes.

What do you think?

]]>