Mentions personal use of superhuman.

Transcript context

…I do feel like a lot of people, you're a seasoned vet, you know, a Vim guide, as you said, right? That's obviously a very minority profile. And I'm comfortable enough to go do command line stuff, but I would probably side more with the typical user who like wants a graphical interface, or at least is more comfortable with it most of the time. Yeah. So that's why I have this maturity model thing to keep reminding myself what the actual goal is and to work backwards. I should not be on the terminal at all in my Pi system. And I should not be in some, I use superhuman, by the way. That's my email client. But I shouldn't be over there. What should happen is I say, what should I be looking at? Who should I respond to? Is there anything important? I just speak those words and the things happen. Whether in the short term, it pops up that client and I have to go interact with it there, or Kai is able to do it himself because he can control the client. I think Gemini is definitely getting there very fast with turning on a bunch of Gemini features in Gmail. But to me, like, no, we should not be dealing with any of this kluge of even an email client is kluj, if you think about it, compared to minority report or the movie Her, right? You remember when you onboard in that operating system, you just say, hey, what's going on? Anything I should know about? And she's, I just read your 940,000 emails. You got a new one from Sarah this morning. That's the interface ultimately I think everyone is building towards. So I try to keep that in mind. I will say one other thing about you, because you're asking about like product advice. The ultimate product advice that I'm seeing, and I help companies with this all the time, especially in cybersecurity, I have this one piece of advice, which is if you are doing a cool product feature in a space like vulnerability management or threat intel or whatever, and it's pretty good, and you are competing against someone who is also pretty good, but they understand the customer and you don't. For example, this is a vulnerability management is a great example for this. Do you know all the engineering teams? Do you know how they push code? Do you know what their repositories are? Do you know how they're measured? Do you know all of those things and their ticketing system and their CI CD pipelines? If you know that and your vault management program or your vault management solution is a little bit worse, maybe than someone else who doesn't have all that context, you are going to lose. Like you're going to lose to the company who has more context. So my expectation is that even somebody who seems like, oh, we just make a task lit and it just puts out this little piece of context, their entire drive, they will either not survive or they will move towards the model of, you know what? It turns out we actually have to learn a lot about this person. We should have a pie for them. And everyone's going to build this deep knowledge of the customer or the user. And that is going to be what powers how good of outputs they can produce, regardless of the product. Yeah.…

Stored transcript either side of the excerpt. The highlighted words are the published quote; the surrounding text is unedited source, never generated.