Timeline for How to structure OOP multiple calculations?
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 31, 2020 at 18:58 | vote | accept | HumbertoWoody | ||
| Mar 31, 2020 at 18:51 | comment | added | HumbertoWoody | @Steve that's exactly what we're trying to solve :) most of our calculations need to be revisited (adjusted would be a better word for it) based on some internal parameters, it's done 2-3 times a week and people that will implement calculation logic is different from the main API team. I am just trying to give a flexible structure for them and us to mantain those conditions and not worry about extra-complicated, separated, data-fetching, coverage validation and calculation execution! Totally agree that probably I need to look at calculations to get a better perspective :) Thank you very much! | |
| Mar 31, 2020 at 8:45 | comment | added | Steve | One piece of advice, if calculations reach the point of struggling to understand "how they're wired", is to try and stay consistent to how the calculations are performed on paper. Computers can perform calculations faster and more reliably than people, but they do nothing to reduce the intrinsic complexity, and if the whole thing cannot be described and worked on paper, then you've probably moved past the point where anyone is truly capable of understanding the calculation. | |
| Mar 31, 2020 at 5:39 | answer | added | Doc Brown | timeline score: 2 | |
| Mar 31, 2020 at 5:05 | history | asked | HumbertoWoody | CC BY-SA 4.0 |