Hey everyone and welcome to Developer Tea. My name is Jonathan Cottrell and we're going to get straight into today's episode because it's a very fast episode. But before we do that, I want you to take a break from whatever you're doing. Take a moment, take a few breaths. Because although while we appreciate how fast things can go and how short episodes are really important for the show, I also want you to recognize the importance of taking things a little bit slower every once in a while. Just taking a breath, taking a moment to appreciate everything that's around you. Appreciate the fact that you actually get the chance to listen to this podcast. It's an amazing time that we live in and I don't want to overstate it. And this isn't a meditation podcast after all, but I do believe it's important to take a few minutes to appreciate the importance of taking a few minutes to listen to this podcast. Take the normal and sustainable pace in your daily life rather than just always going after it, always pushing as hard as you can, always hustling and always moving, you know, just as fast as you possibly can at breakneck speed and sprinting and sprinting and sprinting. Eventually, you will burn out. And in today's episode, we're talking about exactly that. We're talking about not burnout necessarily, but how our motivation, our motivation will change because very often those high level of productivity hours or days or even months, weeks, sometimes years, although rarely years, those periods where we feel particularly energetic about what we're doing. We're highly motivated during those times. And one of the goals of this show is to increase kind of your base level of motivation, right? The higher your, your average motivation level, the more energy you have and not necessarily to work longer hours, but to work better, to invest in that work, to put effort into that work. And so it's not necessarily about working as fast and as hard as possible, but working as best as possible. So what happens when that motivation dips? Because we are not machines and we're not going to continuously have the same level of motivation, how can we deal with this reality? I'm going to give you a very simple tip in today's episode, but first we're going to talk about today's sponsor stack overflow for teams. You've probably used stack overflow to save your tail a few times as a developer. I know I certainly have. And many times the best answers to my most practical questions can be found on stack overflow. But sometimes the questions that I have are really specific to my team. They may be, they may be private information that we don't really want to share in a public stack overflow question, for example. But in the past, the only tools that we had available to us, well, they were kind of insufficient, right? We had to go and dig through our chat message logs or dig through old emails or even I message. Sometimes there's so many different places where we communicate with our team and stacker overflow is fixing this problem with stack overflow for teams with stack overflow for teams. We stack overflow for teams. You have a private and secure home for all of your team's questions and answers. So no more digging through those stale wikis and documentation and lost emails. You can get everything that 50 million people already love about stack overflow and your first 14 days are free. Go and check it out. S dot TK slash developer T that's S dot TK slash developer T get stack overflow for teams today. So we're talking about, uh, what we do. When we, when our motivation dips. And really this is, this is kind of a problem, right? Because so many times the habits that we want to form our motivation cycles don't last long enough for those habits to take hold. And so our default behaviors, we end up resorting to our default behaviors because they're the easiest thing to do, especially when we're low on that fuel on that motivation fuel. So what do we do? Well, there's some very simple advice in this. Advice is inspired by BJ fog. BJ's advice is to prepare for the times that you won't have motivation during the times that you do have motivation. Now, this seems very simple, doesn't it? It seems like an obvious solution. We talked about very similar things in the past when we talked about batch work, right? When you need to come up with ideas, for example, let's say you're writing a blog post, maybe you're a developer and you have a blog and you want to come up with, you know, a good idea. Maybe you want to come up with good ideas for blog posts. One of the best things you can do is sit down and write out a very quick list of 10 or 15 or even 50 blog post titles. Now, the criteria here is that they don't necessarily have to be good. You write out 50 ideas that are just okay. What you'll find is that some will rise above the others. And when you read back over those 50 ideas, if you are going to jump out, and in fact, if only 10% of the people who are going to jump out, well, there's five good ideas for blog posts. And if you were to try to write five blog posts back to back and come up with a new idea after exhausting all of that creative energy, well, that's going to be a little bit harder, right? And part of the reason for this is exactly the same motivation reservoir. You're running out of energy. And so how do you set yourself up for future success? Well, prepare yourself to make those decisions that you're going to make. And that's going to be the first step. The second step is to start thinking about what you're going to do next. And that's going to be the first step. The third step is to start thinking about what you're going to do next. At the last step, a little bit easier. So while you are on a motivation high, you might go through and create some testing architecture for the application that you've been building. Maybe you haven't created the testing architecture yet, but once you create the architecture, writing the tests becomes a little bit easier. And so next time when your motivation is low, you don't have the barrier there of creating architecture first in order to write tests. So instead of viewing your motivation as fuel to get the mundane work completed, view your motivation as fuel to create more capacity. View your motivation as fuel for creating tools, for creating leverage points, where your work when you're less motivated, when you're not as energetic, when you don't have as much commitment, when you're kind of running dry on all that, the easy work is better. The same amount of effort that you put in yesterday, you can put in today, but the outcome is a little bit better because you used your motivated period, the time where you were motivated, to actually set yourself up for better work. This is a very simple idea, and again, it's the concept of batching. Batch the work that will ultimately make you more successful, that will create andensionate your evolution, andensionate your evolution. See you soon. See you soon. See you soon. enable those good habits, batch that work in times where you feel the most motivated. Thank you so much for listening to today's episode of Developer Tea. Once again, thank you to Stack Overflow for Teams for sponsoring today's episode. Head over to s.tk slash developer tea today to get started for your first 14 days for free with Stack Overflow for Teams. Thank you so much for listening. If you're enjoying this episode, then you almost certainly will enjoy other episodes of the show. Go ahead and subscribe in whatever podcasting app you're using right now so that you don't miss out on future episodes like this one. Thank you so much for listening. And until next time, enjoy your tea.