I ended up creating the basic class with the different calculations, and
if future clients need something adjusted, I subclass that and write for
them what's needed. That way, I can rebuild for the new dude, yet not
affect the existing customers since the customer-specific subclass will
not taint the ones previous customers were using.
Thanks everyone for the inputs!
On 2015-11-20 14:31, Ted Roche wrote:
This is the classical test of a journeyman programmer, balancing their
understanding of the situation (the math problem, the way the world
works, what their class of customers has done in the past) to balance
"doing the simplest thing" with "building an extensible framework for
the next change."
We also support a large order processing system. There's an "industry
standard" commission calculation. One customer has their own
proprietary, double-super-secret incentive program that required some
custom work. Of course, everyone else in the business knew what they
did; the sales guys share a beer after work and sometimes after lunch
The next customer who wanted to pay for a commission system used
different inputs, so there's a balance between a generic framework
everyone can use and custom work.
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message:
http://leafe.com/archives/byMID/profox/[email protected]
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
