> Some of these conversations, Ben, I just find them delightful. We have these five whale customers that we’ve talked about, these are active conversations. Active, daily things and in that, the teams are now saying, well, what about the ultra low voltage threshold for the thin pitch library that we’re going to use in this particular cell? “TSMC is giving us these characteristics, you don’t characterize that corner.” Okay, guess what? Go characterize the corner! “Your PDK isn’t as robust as the Samsung or TSMC PDK is to describe the process technology for my team to simulate.”

I get where he's going with this but if you're ever on the other side interacting with a vendor you should be very careful about what, if at all you disclose that their competitors are doing. Vendors notice what they learn from your teams and if they know it is leaky they will not disclose things that make the technical side easier.

At a past gig we used the be the central point of contact for our vendors because we kept a strict firewall on the technical side between different product lines and SoCs.

The first instinct of most engineers when you're trying to evaluate something or get the best performance is to say "X does Y, why don't you do Y" or "X does Y, how can we get similar results" and you've just disclosed something and that vendor will notice. On the flip side if you build up that trust and are known to not disclose you can be read in on things that normally wouldn't be shared. This can be incredibly valuable when you're trying to close on a key technical issue under schedule/time constraints.