TradePort's Guiding Principles for Avoiding Headaches

At TradePort, we have a few guidelines that serve us well. I can attest to their effectiveness, as the few times we've strayed from these particular rules, we've encountered fatigue, headaches, and an insufferable amount of irritation.

The first rule is to operate on a standard data model across blockchains. This may seem obvious, but can you imagine building a consumer app where every chain you integrate has a different data schema? Applications end up fragmented, and features built for one blockchain are incompatible with others. We don't like headaches, so we avoid this approach.

The next guideline is simple but drives many downstream decisions: Nothing custom. If our team can't build it using our public-facing API or SDK—the same ones our customers use—then we either need to update the API and SDK or we don't do it at all.

Lastly, everyone does one project per development cycle. If you have two priorities, you get headaches. And as mentioned, we don't like headaches.