Good Question. What we're doing is very specific to our codebase and processes, and while our parent organization utilizes other systems for ticket-tracking in related but separate activities, they are not good candidates for our procedures. Given that our project already spans six languages and several hundred thousand lines of code, writing a few small modules and a couple of front-end CGIs for this one piece of functionality is preferable to trying to wire our API into someone else's (ill-suited) code. Overwhelmingly the useful functionality already exists in our codebase, and it's really just a matter of coordinating those elements, so I believe I can get this into working shape in probably under a thousand lines of code.
In reply to Re: Re: Decision Trees and the Strategy Design Pattern
by djantzen
in thread Decision Trees and the Strategy Design Pattern
by djantzen
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |