negative engineering is code, or interacting with soft ware systems that you do explicitly to achieve an outcome. defensive code is a great example of negative engineering. It's something that you're writing, when you're writing those tri accepts and everything, you're really hedging against anticipated failure motesthat you're trying to account for. Col: So maybe we should start the conversation in a sort of twofold maybe give us a quick over view of what you might call data engineering, and then what are these negative engineering things that live in that space? Pytin: i think these two concepts are related, but ultimating negative engineerin is deafly more general. Riht as just is way