Lowin: Saving time during outages offers higher leverage than routine orchestration
Jeremiah Lowin · Fireside Chat: Jeremiah Lowin (Prefect), Tristan Handy (dbt) with Matt Turck (Partner, FirstMark) · Dec 11, 2020 · at 32:20
Jeremiah Lowin, founder and CEO of Prefect, explains why Prefect prioritizes reducing time to error during production outages over routine workflow automation.
0:00 / 0:19exact quote · 19.8s
▶ Watch the full episode on YouTube → 720p mp4 · rendered on demand · StarZero watermark
“If you imagine saving someone one hour orchestrating something, just getting that code to run versus saving a team one hour in a production crisis incident, the leverage of that hour, it's the same hour, but the leverage, the impact, the emotional burden, the fact that revenue's at risk versus, you know, just the fact that you've got stuff to go is so wildly different.”
quote is from the automated transcript, cleaned for reading: filler sounds and stutters are removed, nothing is rephrased. names can be misheard (the analysis reads context, assessments check outside sources). how →
More from Jeremiah Lowin
Lowin: Managed hosting for open-source tools is a bad business model
“I think that that is a bad business model. And I sort of, I'm on the record of that. And for a very simple reason, which is that A company that is solving a problem needs to find the correct way to express its knowledge and its solution to that problem.”
Lowin: Prefect's functionality is a superset of Apache Airflow's
“Now it happens that our functionality is a superset of Airflow's functionality.”
Jeremiah Lowin: Every data system eventually requires defining a schema
“You're going to have a schema. It's just a question of whether you define it upfront or you figure it out later.”
Lowin: Prefect acts as insurance, delivering value when data pipelines break
“That's why we frequently describe our product as an insurance product is because we deliver value mainly when things go wrong. And this will sound crazy maybe to say, but if everything goes the way one of our users expected it to go, they really don't Need our…”
Lowin: Negative engineering is defensive work ensuring code actually runs
“And so we've named this problem, the negative engineering problem, because it's not about what you're trying to achieve. It's about all the defensive work you have to do to make sure that it actually took place, in fact, took place.”