How much time do you spend solving negative engineering problems? And can a framework solve them for you? Think of negative engineering as things you do to avoid bad outcomes in software. At the lowest level, this can be writing good error handling with try / except. But it's broader than that: logging, observability (like Sentry tools), retries, failover (as in what you might get from Kubernetes), and so on. We have a great chat with Chris White about Prefect, a tool for data engineers and data scientists meaning to solve many of these problems automatically. But it's a conversation applicable to a broader software development community as well.

Links from the show

Chris White: @markov_gainz
Prefect: prefect.io
Fermat's Enigma Book (mentioned by Michael): amazon.com
Prefect Docs (2.0): orion-docs.prefect.io
Prefect source code: github.com
A Brief History of Dataflow Automation: prefect.io/blog
Watch this episode on YouTube: youtube.com
Episode transcripts: talkpython.fm

--- Stay in touch with us ---
Subscribe on YouTube: youtube.com
Follow Talk Python on Twitter: @talkpython
Follow Michael on Twitter: @mkennedy

Sponsors
Microsoft
Talk Python Training
AssemblyAI