Answered raw tape
D 5 · C 4 · P 4 · Cm 4 4.30
Q Jeremy, that's, that's a little bit the, your story as well, right? Um, that you started building something for yourself and then at some point decided actually other folks may want to use that and it could be an open source project. Is that, is that the story?
A Yeah, it's a version of it. And I was just thinking that when you, when you were speaking, uh, one of the things that I believe so strongly, forgetting the data side for a moment, but when we think about just startups or companies or what it is, is, is solving a real problem and not an invented problem. And if I'm advising someone who's trying to start a company or something, so often you get pitched a solution. Um, but if you asked people if they had that problem, I'm not sure they would recognize it. And so I think that one of the things, certainly that we feel at Prefect and interesting sounds very much like you did with dbt, um, at Fishtown is we were solving a problem that you had that, that I had my background, uh, is as a data scientist and as a machine learning researcher and more specifically in risk management in the investing world. And I had a series of problems that were primarily related to a breadth of work. So across multi-asset portfolios, across many stakeholders, across, and, uh, many of them were analytic. Some of them were not, some of them were somewhat like boring and rote and, and, you know, straightforward. And some of them were incredibly complicated and unproven and experimental and, uh, Prefect was a, was a, you know, an attempt just for myself to solve those problems in a cohesive and unified way. Uh, and most importantly, because I, I mentioned sor…
AI assessment note: “Yeah, it's a version of it.”
Partly raw tape
D 3 · C 4 · P 4 · Cm 3 3.55
Q Great. So where do you sit in that overall ecosystem that we were talking about? I guess, um, maybe double click on the, the, the problem you're solving. What is, um, uh, you know, what is, uh, workflow automation? What does the scheduler do, um, at a, you know, at a high level?
A Yeah, I think the principal problem that we solve There's, there's two, there's two aspects. There's a problem we solve, but before we can get there, let's just talk about sort of what it looks like to, to understand where this problem comes from. Um, people write code. They put that code into the world to do something, to take some action, to have some side effect or produce some results. And, uh, and you build enormously complex and beautiful applications as a consequence of putting all that together. Uh, but making sure that that happens at the right time in the right order with the right dependencies and the right environment and the right cluster. I mean, on and on and on and on is a complicated problem. And often we refer to that as an orchestration problem. And just to like hammer at home. I think it's a very on the nose. Uh, metaphor for it, but you think of an orchestra, right? The orchestra is a collection of individuals who are playing music. There's a composer, there's an arranger, there's a musician, there's a conductor, and again, we have this idea of everything needs to happen at the same time and same, the right time, the right place, the right note, everything like that. Um, that is actually not the problem that we think we solve, though, to be honest with you, because the idea of just running code at the right time in the right place I mean, we can go back pro…
AI assessment note: “What we're actually trying to do is we're worried about the case where”
