Modeling States and Structure: Considerations
Things to take into consideration when using types to make the states and shapes of entities explicit in your code.
— — — — — — — — — — — — — — —
THE CURRENT VERSION OF THIS ARTICLE IS PUBLISHED HERE.
— — — — — — — — — — — — — — —
Tags: #FUNDAMENTAL CONCEPT
This article is part of the Kotlin Primer, an opinionated guide to the Kotlin language, which is indented to help facilitate Kotlin adoption inside Java-centric organizations. It was originally written as an organizational learning resource for Etnetera a.s. and I would like to express my sincere gratitude for their support.
It is recommended to read the Introduction before moving on. Check out the Table of Contents for all articles.
In the previous article, we talked about the benefit of modeling different states and structures of core entities as explicit types. However, as is often the case, this technique cannot be applied blindly, and there are some things you need to consider before you decide to use it.
