As we refactor for readability and scalability, we want to make sure everything that changes between fitting methods is encapsulated so they can be interchanged without touching the core of the code. Interchangeability is to be prioritized above code reuse.
An example class diagram (subject to change) of the vision for the future of the repo is as follows:
As we refactor for readability and scalability, we want to make sure everything that changes between fitting methods is encapsulated so they can be interchanged without touching the core of the code. Interchangeability is to be prioritized above code reuse.
An example class diagram (subject to change) of the vision for the future of the repo is as follows: