eah, exactly. You're going to lose your top performers. And I think very often people are afraid to tell someone on their team when their work isn't good enough because they're afraid of losing them. But that's not a good reason. You should be helping this person to improve. This person deserves to ...
Well, there are lots of different ways to talk about DevEx. One way to talk about it is kind of three key things that have components that are important of themselves, and they also kind of reinforce each other. Flow state is one of them, cognitive load is another, and then feedback loops are another. I think when you touch on this... Your question about flow state is a really good one, and I'll admit we're just a few years into this. We're still figuring out what the best flow state and cognitive requirements are for people in this because, to your point, sometimes we're getting interrupted all the time. You don't just get in the flow and lock down, and write a whole bunch of code and do the typing of a whole bunch of code as much anymore. Instead, you're kind of creating a prompt, getting some code back and reviewing the code, trying to integrate what's happening in the system, and that can really interrupt.
o a key part of this is, this is going to help you stop just spiraling on thinking about what they think about you and gives you something to do that will change that. And then the other key point here is don't try to convince them otherwise. You're not going to go to your manager like, "Oh, I reall...
...at things that come from making it explicit, not just in terms of the increase in decision quality in the moment, but it actually allows you to close feedback loops much better. So that was one thing that I found quite surprising. But the one that I really found very interesting was being told, "Well, what you're...
e don't understand that we are only privy to two out of the three, so I know what's going on for me and I know what I did. I have no idea what happened on your end.