We all believe in ourselves. Even those of us who struggle with imposter syndrome, and most of us do from time to time, we feel that it's important to believe in ourself. And this is an overconfidence bias. It's not necessarily always on purpose. In fact, most of the time, it's probably not on purpose that we portray a sense of confidence that we don't really have a good reason or good evidence to explain why we're portraying that confidence. But it's a little bit tricky because people who have confidence and people who fake confidence often look quite similar. And in today's episode, I'm going to talk about that. I'm going to talk about three kind of confidence smells or overconfidence smells that you can use to kind of establish a picture of your current situation, whether it's for yourself when you start displaying these particular symptoms of overconfidence or with someone else. Finally, a word of caution before we jump into this episode. If you do indeed find out that you are working with someone who is displaying overconfidence. If you do indeed find out that you are working with someone who is displaying overconfidence. Because more times than not, our overconfidence is difficult to diagnose in ourselves. It's difficult to see that we're being overconfident. And this kind of unwelcome criticism, especially when you don't already have kind of suspect that it's true, is likely to be rejected right out of the gate. So let's talk about three smells of overconfidence. My name is Jonathan Cottrell and you're listening to Developer Tea. My goal on this show is to help driven developers like you connect to your confidence. And do better work so you can have a positive influence on the people around you. And before we dive in any further into these smells of overconfidence, I want to talk about today's awesome sponsor, DigitalOcean. DigitalOcean provides scalable compute services, flexible configuration size for any application in industry leading price to performance ratios. You'll get pricing that is consistent across all of your regions at any usage volume. You have rapid provisioning, which means you can get up and running very quickly. With new servers and replica servers. You'll get monitoring included. By the way, this is something that you usually have to add on and configure yourself. But monitoring and alerting are both included with DigitalOcean. And finally, and perhaps most importantly and excitingly, you're going to get $100 worth of free credit just for being a Developer Tea listener. Head over to do.co.tea. That's do.co.tea. To get that $100. Worth of credit. Thank you again to DigitalOcean for sponsoring today's episode of Developer Tea. So let's talk about these three smells of overconfidence. Very simple things. Very simple smells that you can identify in others and in yourself. Now, of course, we're using the word smell in case you're not familiar with this. I encourage you to go and Google code smells. This is kind of a heuristic. It's not an absolute truth. If you see these things, it doesn't mean for sure that. You're experiencing somebody with overconfidence, although basically everyone will have the experience of overconfidence at some point. But these are more like heuristics. They're signs that could be one thing or another. Very often they have to do with overconfidence. The first smell, the first overconfidence smell, wherever there is absolute certainty about almost anything. Whenever someone is portraying the sense. That they are 100% convinced of whatever a particular opinion is. And it seems obvious, but we do this quite a lot. This happens in particular when we get into arguments. When we have to take one side or the other. We very often portray that we're fully bought in to our side of the argument. We wrongly think maybe that this is going to help us win the argument, but very often it actually does the opposite. It drives the other person to back out. To the other side. To back further away into their corner of the ring. Being absolutely certain of really almost anything is a near impossibility. There's almost always a variable that you're not considering. If you shift the context of a given opinion into a different context, then perhaps things have changed once again. We often hear this kind of language when we're talking about code. There's a lot of kind of should language, right? The language where code should be one way or another way. And we're probably even guilty of this on Developer T. Explaining how code should be. This kind of absolutism is really damaging when you're trying to find an optimal solution. When you're trying to be a flexible co-worker. When you're trying to be a flexible worker in general. And a good developer understands that everything has to be taken. And a good developer understands that everything has to be taken. Within its own context. And so whenever you see somebody or you yourself catch yourself with language that portrays that you're absolutely certain about a given opinion. Then you're probably being overconfident. Okay, the second smell. When there is a culture of do-it-yourself-ism. Perhaps the most profound thing that I've learned in my career thus far. Is that if I rely on myself. If I always rely on my own intuition. On my gut. On my experiences. My opinions. My perceptions. If I rely only on myself. Then I'm short-sighting myself. I am kind of giving myself a bad setup. A bad basis to work from. This isn't because my opinion is invalid. It's also not because I'm wrong. All or even most. All or even most of the time. Instead, there's a compounding effect of relying only on yourself. When you're wrong about one thing. And then you work with someone else. And they're wrong about something different. You can kind of cross-check each other. I may be wrong about one thing. But my co-worker is more right about that thing. And so we end up averaging each other out. And if we choose to work with people who see things in the same kind of context. See things in the same kind of collaborative spirit that we do. Then very often we uncover blind spots. We uncover biases. We uncover these lack of skill areas perhaps. And even check each other for example on our overconfidence. But if I only work in a silo. In an echo chamber. Even if I just work with people that are a lot like me. Or that defer to me. They always agree with me. They always give me the floor. If I work in a situation where I make all of the decisions without any checks. Then being wrong about one thing and thinking that I'm right about it. And then being wrong about the next thing and thinking that I'm right about it. This is going to continue compounding. Because I'll create a whole kind of chain of decisions. Where I was wrong at multiple locations. Rather than making mistakes along the way. And improving. So the basis for forming new beliefs. If that basis itself is already flawed. And those new beliefs are also wrong. They're also flawed. Then the new basis becomes even more flawed. So we kind of breed problems in this scenario. And so it's very important when you experience. When you have somebody who is rejecting external input. For example if they say that. Oh well all of those business books on the wall. All of those researchers. They all say different things. So it's all just opinions anyway. This blanket minimizing or rejection of external input. External experience. External research. If you see somebody doing this kind of rejection. Then it's very likely that they are confident. And perhaps overconfident. In their own opinions. And they are probably following something that is. At the very least. Under representative. Of a larger group. A larger collaborative group. And at the very worst. A breeding ground for more flaws. So watch out for cultures. Of do it yourself ism. Where you think that everything that comes in. From the outside. Is bad. Whether that's. A bad thing. Or a bad thing. Or a bad thing. Or a bad thing. Or a bad thing. Or a bad thing. Or a bad thing. Or a bad thing. Or a bad thing. Or a bad thing. Or a bad thing. Or a bad thing. Or a bad thing. Whether that's opinions. Or tooling. Or processes. Whatever it is. Another version of this. Is the Not Invented Here Syndrome. Sometimes the Not Invented Here Syndrome. Is not necessarily related to overconfidence. At much as it is related to fear. So watch for this rejection. This culture of rejection to the external. Especially if it's uniform. If the immediate response. At to anything incoming. is either negative or at best neutral, and then moves towards negative. All right, the third smell, when nothing sounds like a surprise. This one's a little bit more nuanced, but we've all had these kinds of conversations with other people where we're talking about some kind of subject. Let's say we're talking about some kind of research, even research that we did, the person that's presenting this, and the other person presents as if they know everything that this person is saying. They almost automatically say, right, of course, yes, I knew that. And the feeling that you get as the person sending this message to the other person is that this person has seen it all, that they've done it all. They're so experienced that there's nothing new that I can bring to them that they haven't seen before. Now, this is almost certainly not true, and at some point you will see this person experience something that they've never experienced before. Or hear about something they've never heard before, and still avoid expressing any kind of surprise. Whatever the underlying mechanism is for this that tells us that it's going to make us come across as more confident or more trustworthy, very often this does the opposite. Very often it makes you look like a know-it-all or someone who doesn't really, you know, you don't really want to tell that kind of person a story. But the opposite of this response is to listen intently and learn something new in every conversation. Context shift. And asking questions and learning more about this new situation is a much more open way to respond. So it's very important that we think about these things when we go about our day-to-day work. Now, it's not just that we shouldn't be overconfident. Of course, this creates negativity. There are many scenarios in many ways. But it can also be very frustrating to work with an overconfident person. Overconfidence tends to create situations where people are closed off. They don't really want to hear any new opinions. Very often it's hard to work with these kinds of people because if you have a differing opinion, then that opinion is very likely going to be, you know, not accepted very well. And ultimately, the opposite of what that overconfident person desires ends up happening. They end up being ostracized and moved to the edge so that people don't have to try to convince them of their opinion. So I encourage you to always cultivate confident humility. Always be looking for opportunities to ask questions, to be inquisitive, to be curious about what your co-workers think, to be open to the world. And then also recognizing that the things that you see are not the whole picture. That there's always new perceptions, always new ways of thinking. And that the gateway to those new ways of thinking is interacting with the people around you. Thank you so much for listening to today's episode of Developer Tea. Thank you again to DigitalOcean for sponsoring today's episode. You can get $100 worth of credit on DigitalOcean by heading over to do.co.tea. That's do.co.tea. And you can also get a free copy of the book, which is available on the website. do.co.tea. Get started today. Thank you again for listening. If you enjoyed today's episode, and you don't want to miss out on future episodes like this one, I encourage you to subscribe in whatever podcasting app you're currently listening to this episode with. Thanks so much for listening. And until next time, enjoy your tea.