One of the things I've been noticing on my travels across the web is the number of different projects that have all had similar ideas and started their own projects.
I can certainly understand their desire to create something they are interested and share it with others. I have the urge to do the same thing, but instead of putting out code, my approach is one of planning before execution of code. What framework should I use? What balances out with the easiest thing for me personally to implement? What is the learning curve and how long will it take me? Which technologies are most likely to be used by anyone else I might contact? What do I not know that will reduce my chances to produce a workable product?
The primary goal I'd like to already have addressed is that the work could be easily leveraged by another project. I think having many people being able to have their own projects and ideas is a wonderful, varied thing, that should be encouraged. However I am very much aware that most projects don't survive on just the enthusiasm of the core developers. Having code that is freely available to be leveraged by others is needed to help create more chances, more projects, to allow new creativity to fold back into other projects.
So I've added that to one of the goals to address by my project. I am looking to find tools to help separate functions from code, and document and communicate those functions in ways that other ciders and projects can isolate a specific function or feature and then get to the specific code.
No comments:
Post a Comment