@collin I feel all of this! Also, there’s a tendency in programming to make data models or classes as generic as possible to be “as reusable as possible” across different scenarios, but I find that’s usually not warranted in the long run and just results in muddying the waters. I find it’s easier to directly solve the problem at hand, and only think ahead to an extent — avoid going overboard with generic-ness/reusability. YAGNI, and if you do, you can always do some refactoring.