Thanks a lot Adam, Cleaner, safer, modular mifos should be our aim :) regards *ravi
Adam Monsen <[EMAIL PROTECTED]> Sent by: [EMAIL PROTECTED] 20/02/2008 18:45 Please respond to Developer <[email protected]> To Mifos Developer Mailing List <[email protected]> cc Subject Re: [Mifos-developer] *MifOS coding review* On Mon, 2008-02-18 at 14:40 +0000, Ravi Kutaphale wrote: > Recently I started to go through the MifOS code to fix a bug assigned > to me. > Looking at the code I would like to make some comments and want > everyone to *seriously* follow the general coding standards. I can't wait 'till you see the unit tests. :) Ravi, it's a relief to read your comments that should definitely resonate with all Mifos developers. We feel your pain. In fact, I recall a slide from a presentation on Mifos that put a metric on that pain. And I couldn't agree more with Keith and Van's latest comments urging clear intentions when writing identifier names, following patterns, etc. Self-documenting and intention-revealing code is critical to: * scaling our development effort (thank you Rob Short) * having an agile and adaptable codebase * having a maintainable codebase Better code means better Mifos, means helping people out of poverty more effectively! -- Adam Monsen ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
