> comes from understanding what that code is really doing It does come from understanding the !business code! that is involved. Not the rarely important featur

> comes from understanding what that code is really doing It does come from understanding the !business code! that is involved. Not the rarely important features of the underlying language that the stack, the framework or the models handle. Which makes that argument further moot - you should not be messing with how the models or the framework handle those data types. There is a reason why they were built and deployed.