Monday, July 10, 2006

How are we really taking advantage of code reusability?

This is something we always wanted, and now we have the tools to take advantage of it, but yet, the way companies are structured, there's no interest in having a universal library of coding modules.

I mean we like, it feels a niche, but we need something a step up, where we can share full coding modules.

And this is also part of the difference between coders and designers, designers can show web designs and portfolio's, what can we really show?

So to fulfill two needs, our community should create a new type of modulare code sharing.

Here are my simplistic ideas for the structure of this code sharing community.

People would submit code, and put it into a category, registered members would review, and rate the code.

The code submitted should be framework neutral, something that could be used in almost any method. That of course could change as the amount code modules were available.

You can view the code, download the code, test the code, except code that is database specific, or File IO Specific.

Also other members can try to compete against the same code goal, and see if they can write it better in any of the following ways:

1. Clearer Documentation
2. Scalible to different levels of needs
3. Can it be done in less lines of functionality
4. Is there a version of it, in each of the popular frameworks of the times?

Etc. Keep it simple at first, but competition would provide coding examples of what good code was, and make good code available to beginners, or those who want to deliver products/services faster.

Rapid Application Development

There would also be a Dreamweaver Extension or Webservice, where you can browse, view, or download modules as you had a need for it.

I just had the idea, does this interest people?


  1. Anonymous5:34 AM

    What's the plan for organizing this code? Using class libraries? Something like PHP's Pear packages?

  2. I am open to ideas, the main point is if reusability is so important, then it should be applied to coding..

    So that instead of doing the old coding generator's, we can create apps, made out of modules we can easily transform into specific needs.

    And that would improve the quantity of apps being turned out.

    But use a rating system and contests to also help us improve our quality.

    As far as to how they'd be stored/displayed, something like but with ratings, and a webservice/extension combo to allow us to browse modules and see waht we need for the app we're creating.

  3. Anonymous6:38 AM

    > How are we really taking advantage
    > of code reusability?

    I don't understand. What has company structure got to do with reusability?

    Increasingly, the industry standard approach to promoting reusability is by building components that are cohesive and loosely-coupled, and using tried and tested design patterns to structure applications.

    These approaches are now the closest thing we have to a universal standard methodology/approach, IMHO.

  4. Well i find it rare to be in a circumstances where the company i have has a shared library of modules/snippets

    Or will allow any of their code to be released publicly to help other coders

  5. So when do we start?