[BW-dev-discussion] Is it important to adopt a new framework before proceeding?
2010 at samu.cat
Mon Aug 23 03:48:38 CEST 2010
I'm in the list just for keep updated, and my experience in plain code is little, but
As i read over the time from BW coder and own other projects experience; I'm with Peter on this point:
On 22/08/2010 10:47 PM, Peter Lind wrote:
> I would offer the following idea:
> 1) keep the old system in place
> 2) implement a new framework on the side
> 3) code every new feature in the new framework. Migrate existing
> features to the new framework as needed
> This avoids a big-bang strategy (one of the most likely risks of
> failure for the project) while easing developers in.
Only cover bugs or minors in the old system.
Call to all coders (even the old volunteers) for sitting (virtually), and get the chance to rearrange or change as needed.
Reuse as much code from the old system to improve work time on the new framework, but never dropping the possible improvements on the name of time. (as we know the snow balls grow...)
I'm conscious that it is easy to talk when my effort/time/even ego is not involve.
May be now is the opportunity to re make the tool as a (full) reusable open source application.
In any case, Thanks to all codes involve to make BW possible.
More information about the bw-dev-discussion