[SoftTalker]

> you could easily end up with bugs that only show up when the transaction isolation level changes from how you tested it.

In fact it's very likely you would. You have to understand the transaction semantics and test with all the isolation levels and database platforms you intend to support. If you don't know this, you need to learn more about relational databases before building a product on top of them.

[JoshuaDavid]

> If you don't know this, you need to learn more about relational databases before building a product on top of them.

And now extend this principle to everything in the stack.

[smy20011]

You should at least have some basic ideas about your stack.

[JoshuaDavid]

Agreed. But also if you suddenly find that the precise behavior of one of the parts of your stack matters, you would be well advised to search the internet about how exactly that bit works in practice and whether there are any nonobvious footguns in addition to your empirical testing and the stuff that the manual claims is true.