Disclaimer: just a random impractical advice, you can safely ignore
I think I don’t necessarily change my view, the most good principles can be applied to ReScript as well. A really good principle don’t care what language I’m using.
What changed from ReScript to TypeScript is, we have a good tool, variants for controlling simple cases better, clearly.
So, it’s really depending on myself, how simple I can make and settle with. And I don’t actually need to make it less complex as always. Complexity can explain more, and gives me more control.
I recommend this article, explained well in a bit formal way.
https://www.lesswrong.com/posts/HNJwteaxpRYfLaQt7/tradeoffs-in-complexity-abstraction-and-generality
And the most effective way to get insight of data design is a deep understanding on the specific domain and experiences. So I usually do deep research the problem first, which isn’t productive way at all.
Or just get it might break everything, but also fixable. I’ve heard that all the wise people work in this way.
ReScript at least helps fixing the codebase.