Timeline for Flexible (dynamic) user input vs statically typed language c#
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 20, 2019 at 1:45 | history | edited | Vector Zita | CC BY-SA 4.0 |
Minor fix to improve how meaning is imparted around a couple of small details.
|
| Sep 3, 2019 at 0:02 | comment | added | Vector Zita | @DavidY no problem! Because I feel I did not really state this clearly, your problem is (was?) that your attempted solutions are based on trying to model a Data Record, which is a notoriously meaningless abstraction. Forget them and try to build actual domain classes. Remember, you want your classes to be as clean and expressive as possible. To have roles. When composing them (i.e. your representation of the domain), try to not think about how they come to be (i.e. how they are instantiated) but how they are to be used, so compose them in a way that helps you solve your actual problem(s). | |
| Sep 2, 2019 at 23:30 | comment | added | DavidY | Thank you so much for the detailed advice. This is exactly what I am looking for. It will take some time to digest ---- I need to clarify the relationship between domain logic and use cases and consider refactoring the calc engine. I will also look into the anemic domain models. | |
| Sep 2, 2019 at 23:19 | vote | accept | DavidY | ||
| Sep 2, 2019 at 20:02 | history | edited | Vector Zita | CC BY-SA 4.0 |
Included a small code excerpt to highlight the key points of the answer.
|
| Sep 2, 2019 at 19:47 | history | answered | Vector Zita | CC BY-SA 4.0 |