I worked on one of those many years ago. I think it had 200 line function in the middle that was a line from line port from a basic like DB programming language that was basically unrefactorable if you wanted to get the same results.
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Speaking from experience, it looks so easy (just divide then subtract some totals) but quickly devolves into a tar pit of business rules, race conditions and consistency errors. It’s worth paying someone else to do this!
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
We had to put “approximate charge” on a page because our provider calculated by the second. So between rendering the confirmation page and a user clicking the amount could change.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
throw in leap year bugs to that proration code that never get fixed because systems team always say “we’ll have a new system in four years, no need to fix the root cause” but then eight years later you’re still on the same system...
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Proration logic with taxes. Add to it generating data for Accounting at line item level and arithmetics become hard
-> I learned that balancing amounts on millions of items is hard (worked on billing/invoicing for years for Telco companies before everything became unlimited)Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
And discounting. I'm convinced that with sufficiently baroque discounting schemes nobody actually knows what the price is supposed to be.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.