I'm all for ripping out the financial code and replacing it. And I share Erik's concerns about stability.
Would it be possible to start by defining an API that wraps the current code, write some tests against that API, and then be able to use that to verify that the new code works correctly?
I'm thinking either a database API of stored functions, or a web services API. If we could get that in place with some decent tests, we can then totally change the underlying schema and know when we have it successfully built. TDD. And we know we want both -- much of the app in the database, as well as a REST API.
Just a thought...
On 01/22/2014 12:55 AM, Chris Travers wrote: