Hey everyone and welcome to today's episode of Developer Tea. My name is Jonathan Cottrell and my goal on this show is to help driven developers like you find clarity, perspective, and purpose in their careers. Today we're talking about the thing you know you need to do. The thing that's sitting in front of you that you've been putting off. I'm not just talking about the hard task in your current sprint, although that could fit this mold in some way. The thing that you know that you need to do, that you need to address, that's not going to go away. The thing is that we often try to find ways around our hard problems. It's not because we're lazy, it's because this is part of what it means to be a human. It works. We are looking for ways to reduce the load on our brains and get ahead. We want to get more done sooner. We want to get past our obstacles and accomplish things that matter more to us than getting through the obstacle. And sometimes this works, which is kind of a reinforcing loop. We can hack our way around a particular problem and not have to deal with the hard parts and then jump ahead. And so we start to model. More of our problems in this particular manner. We find shortcuts here and there, and therefore we start looking for shortcuts everywhere. And it becomes the way we imagine just accomplishing everything. But the truth is that there are aspects of your job. There are aspects of your life, of your relationships, of your career, of hobbies that require that you do something. That is difficult. That's messy. That is slow. That is inefficient. That requires some deep level of thinking. Something that you have very little skill in doing that you have to try over and over and fail over and over at. These are the hard things that we have to face. And it's very likely that you have a hard thing that you already know about that you've been trying to avoid. Now, not everything that we're trying to avoid is worth doing. But many times the things that are worth doing are hard enough that we do try to avoid them. In other words, we procrastinate. We find reasons to do something else first. We imagine that we're eventually going to strike gold and find another path to where we're trying to go. But we're not going to do that. But most of the time, that same obstacle, whatever it was the first time, is going to come up again and again and again. Whether that's the domain knowledge that you need to be able to operate with some level of authority in your current role at your current company. Maybe it's the relationships that you haven't developed that you know you need to develop that you keep on running into problems with. Maybe it's a coworker on your team or maybe your product manager. Maybe you and your boss have not really carved out any kind of personal connection yet. And you may not even have any conflict there, which is why it's so tempting to kick the can. To not do the thing that you know needs to be done. The most important part is that hard thing that you're procrastinating on. So I want you to imagine that this is never going to go away. Try to figure out in your mind while you're sitting here listening to this. Write down two or three of these things that you know that's something that if I were to have done it already, a problem would be removed from my path or I will have grown in some significant way. If I would have repaired the relationship. With my boss or deepened it. Then maybe I wouldn't be so afraid of losing my job. Right? Or maybe I would feel more comfortable asking for an alternate alternative position. Maybe move to a different team if my boss and I were on better terms or if we were closer. Right? So thinking about the consequences of this because if you're like most people, you're trying to find a way. To do that thing to get to that other team that doesn't require you to go the hard path of improving your relationship with your boss. Right? So similarly, if you want to become a great engineer, a great Python developer, for example. A lot of people want to read a book or a tutorial or find some kind of tool or even lean on AI to teach them more. Right? Teach them more about Python. But the hard path is building things over and over. Building things over and over and over. Getting feedback from other engineers. Getting those reps of building things and not just building things for the sake of building them, but building things that actually challenge you that actually, you know, push you to to put the things in practice. That you're learning. There is no easy button to become a great Python engineer. Ask any great Python engineer how they got there. And I can almost guarantee you that they're going to answer by saying, by building a lot of stuff and having other people tell me what was wrong with it. Or some form, some variation of that. And that's true, not just in Python, for just about any specific technology that you can find. Okay. So instead of hacking your way into your next job, instead of figuring out how to keyword stuff your resume the perfect way, what is the hard thing that would help you more? The hard thing like developing a relationship with the recruiter at the company that you are thinking about moving to. What's the hard thing that helps you start your own business or helps you move from being an individual contributor to a manager? What are the hard things standing in your way that if you were to have done them, if you could check off the box, you would. If you could say, oh yes, that's behind me, then everything else becomes easier. Now, trying to answer the question, why haven't you done that? Why haven't you taken most of your energy and put it towards the hard things that would actually move you forward? The majority of the time, the answer is because we think that either we're too busy, which is probably a lie, or we think that there may be an easier way. And so our rat race... Our rat race in our mind is running on overdrive, trying to find a way around this thing. And the difficult answer is being honest about that and saying that your next step should be to give up on all of those alternate pathways that could be faster. It could be easier. It could be lower investment. Right? And choose, make a decision to go with that hard path. So it's very uncomfortable to do this. In fact, I can show you how uncomfortable it is by asking you to do it right now. Pick one of those things on your list. It doesn't have to be all three of them. That would be really difficult to do. Right? Just three, four, whatever you have written down. And make the commitment right now. Now to do one of them. It's going to be hard. It's going to be really difficult. So difficult that I think most people listening to this right now may even pause this episode. It's such a hard thing to do. Why is that? Why is it difficult to make the decision to do a hard thing? It's not even the actual act of doing the hard thing. It's the decision to do the hard thing. It's because we're giving up on all of that. We're giving up on all of these alternative pathways. We are letting those things go. Which means that we've opted in to something that's going to take a significant amount of our time and energy. And we've opted out of everything else. Choosing to cut off our optionality is painful. And this is one of the core reasons why doing hard things is hard to even do. And it's hard to even start. It's hard to even start to make a decision. To do the thing that you know you need to do. Because you are choosing not to do a whole myriad of other things. You're closing off your optionality. I can almost guarantee you that if you were to choose to do one of those things that you know you need to do. You would be better off for it. I'd encourage you to try it. I'd encourage you to write down that commitment. Go talk to your boss today. Make the... Whatever that... Whatever that... Whatever that... Whatever that... Next committed step is. And then figure out what the first step is towards actually doing that hard thing. Take the first step. At the risk of sounding like a motivational speaker. This is actually one of the most difficult things to get motivated about. And so hopefully you're listening to this. Hopefully you're not hearing me trying to hype you up. And have you just lean on the motivation feeling that you have right now. The... The energetic feeling that you might have hearing this. That won't carry you through this. It won't carry you through the obstacle. It may carry you through the first round of combat with the obstacle. But it's not going to carry you through when the hard parts start happening. When you start screwing up. When the relationship development is awkward. Right? The conversations with your boss are awkward. Or they're not going as expected. Or maybe your boss delays your... Your one-on-one. Because he doesn't quite have time for it. That's when things get hard. And it's easy to throw in the towel. And that's when you have to come back to this episode. And remind yourself that you're... You may see an out in that moment. You may see, okay. I'm going to open my options back up again. I'm going to decommit. I'm going to move back away. I'm going to backpedal out of that. And I'm going to see if I can figure out another way forward. And that's almost always going to be a mistake. Right? So... So... Come back to this episode. Listen to this again. So that you can reinforce why you're choosing to do this. What about that specific obstacle is going to carry you forward to the next place you want to be in your career. In your life. You know, as an engineer. In your skill set. Whatever those things are. If you can stay committed to that reason. That underlying reason why you're doing it. Your core motivation. Then you're more likely to stick with whatever that commitment is. Thank you so much for listening to. Today's episode of Developer D. I hope you enjoyed this episode. I hope that it was somehow enlightening for you. Maybe you haven't thought about why. You know, what the relationship between you and the kind of avoidance mechanisms. Why did those exist? You know, how should we listen to those things? Should we always do those things? Probably not, by the way. We didn't dive into when your inner voice may be kind of leading you the wrong path. But... But... But... But... But... But... But... But... But... But... But... But... But... But... But... But... Thank you.