Completely agree, show me the data and I'll tell you if your solution matches the problem you are trying to solve.
So much impedance is unclear thinking and overly complex solutions, it usually combines with inconsistent naming schemes across the stack.
It's easier to gatekeep if you're the only who knows a "game" equals a "contestQuest" because you've created some overloaded polymorphic "quest" system in your backend.
So much impedance is unclear thinking and overly complex solutions, it usually combines with inconsistent naming schemes across the stack.
It's easier to gatekeep if you're the only who knows a "game" equals a "contestQuest" because you've created some overloaded polymorphic "quest" system in your backend.