Beefy Boxes and Bandwidth Generously Provided by pair Networks
Syntactic Confectionery Delight
 
PerlMonks  

Re: Decision Trees and the Strategy Design Pattern

by theorbtwo (Prior)
on Dec 26, 2002 at 03:25 UTC ( [id://222274]=note: print w/replies, xml ) Need Help??


in reply to Decision Trees and the Strategy Design Pattern

My first question when seeing somthing like this is always (OK, it often isn't, but normaly should be) why aren't you using an existing system? It's by thinking about the problems with other WTDI that we come up with how the best way to do it is for our situation. If the reason is "a bad case of instutional NIH that I can't do anything about" or "for the fun of it" (in which I include "to learn"), that's one thing, but if the reason is "because I havn't looked at them", then that's somthing else. If there's some specific shortcoming, think about what caused that shortcoming very carefuly, so as to not duplicate it. At the same time, of course, you must be careful not to fall into an opposing trap.

I'll render another oppionion after reading your post -- perhaps.


Warning: Unless otherwise stated, code is untested. Do not use without understanding. Code is posted in the hopes it is useful, but without warranty. All copyrights are relinquished into the public domain unless otherwise stated. I am not an angel. I am capable of error, and err on a fairly regular basis. If I made a mistake, please let me know (such as by replying to this node).

  • Comment on Re: Decision Trees and the Strategy Design Pattern

Replies are listed 'Best First'.
Re: Re: Decision Trees and the Strategy Design Pattern
by djantzen (Priest) on Dec 26, 2002 at 03:52 UTC

    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.

Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: note [id://222274]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others examining the Monastery: (2)
As of 2024-04-20 03:12 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found