Paul Dix
๐ค SpeakerAppearances Over Time
Podcast Appearances
Not right now.
like what would it take to get it there so with a with a prom ql implementation i think the two things that are most important are one uh compatibility which actually like i have a high degree of confidence in the compatibility piece because of the test suite that's in the prom prometheus code base right uh but then the other thing is performance so just in terms of like the pure like
what I think makes a good Prometheus implementation is those two things, right?
Performance being like how fast are the queries, but also like performance in terms of like what's the infrastructure footprint to handle a given workload, right?
And that's more dependent on like the core pieces of the database, which is actually our focus right now.
So, but then the other question is like,
You know, we talk about this internally as engineering leaders, and it's like, what engineer is going to support this?
You've got 60,000 lines of code that wasn't written by you or anybody else in the company, right, is written by Claude.
Or Claude and Codex.
On some level, that is my argument, too.
It's like, okay, well...
you have the robot to help you out right but i i will say which i agree with right there's no there's literally no engineering problem i can think of right now like software engineering problem i can think of right now where i wouldn't as a first stop use an agent
to talk through the problem, to do an investigation, to explain to me about the code, right?
If it's a new code base, even if it's a code base, I know my first stop is going to be like, fire up the agent and start iterating, right?
And start investigating, right?
Just because they do it, like it just- It's so much faster than doing it yourself.
Exactly, exactly.
Yeah, well, so for example, there's this new set of capabilities we're working on right now, which we do intend to release.
And there was, you know, there was like a core change that I had to make towards the end of last year that was based on a workload that we had seen that we weren't able to handle.
And I was like, OK, I need to make this change.