Robert Mustacchi

Another example is a colleague was asking about, hey, I'm trying to get more into some of the PCIe hot plug stuff. Can you help me understand how this actually all fits together with this? Because the PCIe spec is long and involved and not the easiest thing to read. So, you know, then the answer to that is, you know, yeah, let's find a time that does this and, you know, get into it.

Another example is a colleague was asking about, hey, I'm trying to get more into some of the PCIe hot plug stuff. Can you help me understand how this actually all fits together with this? Because the PCIe spec is long and involved and not the easiest thing to read. So, you know, then the answer to that is, you know, yeah, let's find a time that does this and, you know, get into it.

And I think that's, that's partly how you do that. And then helping make sure folks feel that it's okay to ask those questions too is equally important, which, you know, is always an ongoing effort to kind of build those reports because you can't, you can't necessarily know someone's struggling. So all you can do is try to be open and willing to answer stuff and try to be helpful.

And I think that's, that's partly how you do that. And then helping make sure folks feel that it's okay to ask those questions too is equally important, which, you know, is always an ongoing effort to kind of build those reports because you can't, you can't necessarily know someone's struggling. So all you can do is try to be open and willing to answer stuff and try to be helpful.

I wish I could claim omnipotence or something like that, but that clearly – or something like that.

I wish I could claim omnipotence or something like that, but that clearly – or something like that.

Yeah. I mean, I think, um, that's a good question. I think a chunk of this I picked up from just working with Keith over the years. Um, yeah, Keith's also very, very good at it. There's a lot there, but, um, I, I think this sometimes gets back to, uh, you know, the earlier kind of a code review is really trying to ask why, um, Yeah.

Yeah. I mean, I think, um, that's a good question. I think a chunk of this I picked up from just working with Keith over the years. Um, yeah, Keith's also very, very good at it. There's a lot there, but, um, I, I think this sometimes gets back to, uh, you know, the earlier kind of a code review is really trying to ask why, um, Yeah.

And really trying to understand how does this fit into the system? How is someone going to do this? Or if someone wants to do X, what else does that mean they need to be able to do? Or how does it work? For some of this stuff that we're seeing around, I think some of it's cheating that we've been thinking about for over 10, over a decade. Dog patch is 2014. It's 2025. Yeah.

And really trying to understand how does this fit into the system? How is someone going to do this? Or if someone wants to do X, what else does that mean they need to be able to do? Or how does it work? For some of this stuff that we're seeing around, I think some of it's cheating that we've been thinking about for over 10, over a decade. Dog patch is 2014. It's 2025. Yeah.

So someone's just had a long time to just marinate in the back of the head with just different experiences. And I think part of that also is just a bit of just, um, you know, paying attention to how to, how are folks using things? How's opera, how are operators using things? Um, I don't know. I don't know. I wish I had a better answer for you there. Uh, so I could, no, no, no, no, no.

So someone's just had a long time to just marinate in the back of the head with just different experiences. And I think part of that also is just a bit of just, um, you know, paying attention to how to, how are folks using things? How's opera, how are operators using things? Um, I don't know. I don't know. I wish I had a better answer for you there. Uh, so I could, no, no, no, no, no.

I think, I think a lot of it is just trying to, A lot of it's listening, and then a lot of just digging and really needing to understand the low-level details before you can kind of go and make the high-level answer and how the two inform one another.

I think, I think a lot of it is just trying to, A lot of it's listening, and then a lot of just digging and really needing to understand the low-level details before you can kind of go and make the high-level answer and how the two inform one another.

Yeah, and I think that often just comes back to some, let's say, just scar tissue and experience, right? Some of it was we've had times where we couldn't upgrade firmware or we couldn't get, you know, we didn't have the tools to or even get firmware updates. And so we've just been burnt by that over the years. And so I do think there's also just, you know...

Yeah, and I think that often just comes back to some, let's say, just scar tissue and experience, right? Some of it was we've had times where we couldn't upgrade firmware or we couldn't get, you know, we didn't have the tools to or even get firmware updates. And so we've just been burnt by that over the years. And so I do think there's also just, you know...

you really want to think about how you approach and think about uh firmware and just you know just the same way it's like software and just that it's not this uh while it can be very hard to understand just because of the um specifics of the way you know you're working with vendors you know obviously um if you just get a binary blob it's hard to really get into there but you know it's a thing that can fail and needs to be updated just like anything else so um

you really want to think about how you approach and think about uh firmware and just you know just the same way it's like software and just that it's not this uh while it can be very hard to understand just because of the um specifics of the way you know you're working with vendors you know obviously um if you just get a binary blob it's hard to really get into there but you know it's a thing that can fail and needs to be updated just like anything else so um

I suspect that if we probably go back to Dogpatch, we probably have some commentary on the firmware that we were dealing with and just the operational problems there and trying to figure out how do you get to a better model? Where even is all the firmware? If it's there, assume something's going to go wrong. Or if there's an EEPROM that has data, assume it has to be flashed.

I suspect that if we probably go back to Dogpatch, we probably have some commentary on the firmware that we were dealing with and just the operational problems there and trying to figure out how do you get to a better model? Where even is all the firmware? If it's there, assume something's going to go wrong. Or if there's an EEPROM that has data, assume it has to be flashed.