What is on your mind? It seems like a simple question to answer. Anything that you're listening to or thinking about or looking at. Something maybe that happened a few minutes ago or yesterday or maybe even a memory from years ago. Or maybe something that's happening later on today. Something that you're anticipating. But it's likely that if I were to ask you what's on your mind at any given point in time, you may be able to have an answer for me. You may be able to answer very quickly what you're thinking about. This isn't always true and in fact, sometimes it's difficult to even know what we're thinking about. As an exercise, I encourage you to try some form of meditation to see just how difficult it is to direct your thoughts. Those of you who have tried meditation, you know the frustrating feeling of not being able to turn off your runaway mind. But in today's episode, we're going to be looking at this question from a different angle. More specifically, we're going to be looking at the antithesis of the question. What are you not thinking about? And of course, the answer to the question is relatively infinite, right? But we can refine this question a little bit more. And direct it at our own behaviors. What are the things that we encounter that we're not thinking about? And that's what we're talking about in today's episode. My name is Jonathan Cottrell and you're listening to Developer Tea. My goal on this show is to help Driven developers uncover their career purpose so they can do better work and have a positive influence on the people around them. And in this particular episode, we're going to be talking about ways that you can inspect your defaults. That you can try to push a little bit on the boundaries of your everyday life. And try to find things that you're doing or that you've kind of set up as your experience. Things that you really are not evaluating. Try to uncover what those things are. And more specifically, what you would do without them. So this concept of defaults. This concept of defaults is something that we've talked a lot about on the show. There's plenty of research to back this up. But everything that you make a default becomes much easier for you. It's easy to choose the default option. And if you set yourself up to have good defaults, then you will make better decisions more easily. This is a very simple concept. That if your default way of operating supports healthy habits. For example, for developers. If your default way of developing software is to always start with a good habit. Always start by, for example, writing a test. Then it's more likely if you set up that default as the everyday behavior. That you're going to continue that. Because making that decision is no longer a choice. Instead, you have to choose to stray from the good habit. And this is something that most people. Once they've established a good habit. They want to continue that good habit. And the anomalies are the times where they stray outside of that good habit. Think of someone that you know that eats very well. They have a very good diet. A balanced diet. They're healthy. And every once in a while that person will enjoy birthday cake with everyone else. Right? But by a default rule. They don't indulge on a daily basis. They've set themselves up for a healthy default. Now what I want you to do. Is to start inspecting your defaults. Don't just actively create new defaults. But look at the ones that you already have established in your life. And this is actually a little bit harder than it sounds. Because in order to understand your defaults thoroughly. You might just have to go through some uncomfortable situations. We're going to talk about that. And just a little bit later. After we talk about today's sponsor. Bitrise. With Bitrise. All of your deployment processes. And we're talking about from the most simple to the most complex. Bitrise makes those things easier. And Bitrise is specifically for mobile continuous delivery. And you can take these various blocks that Bitrise has. They have over 170 integrations available. And you can take these integrations. You take visual blocks and put them together. Kind of like an if this then that. But even more powerful. Because you can put as many of these blocks together as you'd like. And it's not just the technical stuff that they cover. They also allow you to send alerts to yourself in Slack for example. Whenever your build finishes. Whether it succeeds or fails even. You can send yourself a Slack message. Of course. You can send it to a lot of developers. You may not want to use a visual interface. And of course. You don't have to. Bitrise allows you to edit a YAML file. To kind of define this workflow. And then you can use that YAML file. And share it with everyone else. And everybody's going to be using the same processes. Go and check it out. Spec.fm. Slash. Bitrise. Thank you again to Bitrise for sponsoring today's episode of Developer T. Imagine that you hire someone. To watch you. On a daily basis. And to record every action that you take. And somehow this person has psychic abilities. Or some other way of reading your mind. And they also record every thought that you have. And they're such a good recorder. That they can record your heartbeat. They can record the steps that you take. Where you travel and when. Of course everything is going to be time stamped. In this super log. That this person is amassing. And if you were to have this amazing picture. Laid out in front of you. I want you to imagine if you were to stack all of those together. One day after another. All of these logs. Of things and behaviors. Specifically that you have. Now of course. We aren't going to be talking in the direction of the quantified self. Although we very well might have a guest on. That talks about the quantified self very soon. So make sure you subscribe if you want to miss out on that. It's going to be a great discussion. But instead I want you to look at. What things will stand out. As patterns. So for example. If this person is. Recording the time that you open your computer. For the very first time every day. How much variation. Will you have. How much variance will that. Time stamp. Have. From Monday to Tuesday or Wednesday or. Even from Monday to Monday. Since we typically structure our weeks. As a unit rather than individual days as units. If you take five Mondays how different. Are those Mondays going to look. And more specifically. How similar will they look. If you're like most people. Then. Most of your days are going to look. Quite similar. You're going to open your computer for the first time. Sometime between. You know 730 and nine for example. Of course this isn't a. Scientific explanation of real data. This is just. A possible reality for someone. They likely will open their computer between 730 and nine. And we actually see this. As kind of a. Base rate we can identify. Behaviors that not just us but. Society in general has. For example. Most people check their email or social media. Immediately when they wake up. And so we start identifying patterns that we have. In this super log that this person is. Gathering and. We can start to see things that we do on a regular basis. And these things are. Essentially our defaults. The variety in your diet or. The route you take to your diet. Or the route you take to go to work. Or the things that you. Consume media wise or. If you're like most people maybe you feed yourself. Your own opinions. You. Find information that agrees with you and. You continue to deepen. Into the same direction that your opinions already are. Of course you very well. May find some interesting and positive defaults. In that list. For example if you're like me then you try to set up a default that. Every day you're going to exercise and that in order to not exercise. You would have to. Plan that. In other words you don't put exercise on your calendar. You put don't. Exercise. On your calendar. And this is why it's so difficult to evaluate. You don't go to your calendar to find this information. For example. You probably leave work. At the same time on most. Days and. That's probably not necessarily on your calendar. So of course we've established the idea that defaults are important and. Understanding what it is that we do every day. Is important as well and. It's important that we understand the defaults that we haven't intentionally. Created. We've also established that this can be very difficult. It's difficult to understand exactly what we do. Our own behavior is kind of a mystery to us. And while I can't give you every answer of how to uncover your own behavior for yourself. One thing that you could try. Is what I call subtractive behavior. So this is a very simple concept. I want you to. Imagine your day. Without a particular element. In your day. And more specifically for developers. I want you to imagine working on a project. Without using a particular. Technique. So if you're writing JavaScript. Maybe. You no longer allow yourself just for one day. You don't allow yourself to use a part. Of the language. You put some kind of constraint on. The actions that you're taking. Maybe you don't allow yourself to use ternary operators or. If statements. For example. Now why would this be useful? What does subtractive thinking. Do. Well I want to use a simple metaphor to describe this. I'm going to use a simple metaphor to describe this. I'm going to use a simple metaphor to describe this. Imagine that. Your behavior. Is kind of like a river. And in that river. There's various rocks. And there's land formation. And there are. Places where the river goes downhill. More steeply than others. And there's even erosion. And things that are changing over time. Even though they may not necessarily be changing right in front of your eyes. Now imagine that the river. Instead of the water. Becomes. Clear. Instead of the water being clear. It is very murky. In fact. You can't see the underlying structure. Of the river bed at all. You can't see the rocks. You can't see the. Sticks. Or the animals. Or how deep. Or shallow. That river is. And it's even difficult to see how quickly it's flowing. In many ways. This is like our behavior. We know where the water is going. We know generally. How we behave. We have some insight into our personalities. And some people have more than others. But generally speaking. We know. How that river flows. But we don't know. What is causing that flow. To be exactly the way that it is. And so. When we subtract. That's kind of like. Reaching into the river. And pulling a rock. Or a boulder. Out. Of the river bed. And we watch how the river's flow. Changes. Now the interesting thing. Is that. A very small rock. Could have a large effect. Or a small effect. It depends on the placement. And as we remove. Items from that river bed. And as we. Change the way that the water is flowing. We can start to. Realize. What the effects are. Of those various behaviors. Of those various boulders. Rocks. Sticks. We can start to. Understand. That if we. Look at the river. And see. How the water is flowing. We can start to. Realize. What the effects. Are. Of those various behaviors. Of those various boulders. Rocks. And understand. That if we. Put that. Boulder back in place. What it will do. To the behavior. Of the river. To the flow. Of that water. Likewise. For our own behavior. When we subtract. We can start to see. Some interesting. Effects. I'll give you. A very simple. Example. Something that you do. Probably multiple times a day. If you're like most people. Probably three to five times a day. Most people. Eat. Three to five times a day. And that's. What the effects. Are. Of those various. Effects. Of the water. And that's. Something that you can. Try. To do. If you're. In the category. Of people. Who only. Eat. Three meals. A day. If you want to see. The effect. Of subtraction. Try skipping. Just one meal. Another. Simple. Example. Of this. Try. Skipping. The first. Three hours. With your screen. In a given day. Whether. That's. What your life. Would be. Like. If you subtracted. That small. Rock. Out of your riverbed. How does. The flow. Of your life. Change. And the goal. Here. Isn't necessarily. To. Remove. Everything. Out of the riverbed. I'm not going. To tell. You. That you need. To. You know. Give up. Your screens. Entirely. For example. Of course. The goal. Of subtractive. Behavior. Or subtractive. Experimentation. In your behavior. Is to. Understand. Just. How. Much. Of a. Lynch. Pen. Or. How. Effecting. That. Particular. Thing. Is. To. Your. Life. Another. Simple. Subtraction. Behavior. Try. To.! To. Your. Life. On. A. Day. Without. A. Clock. This. Is. A. Single. Subtraction. Really. You're. Subtracting. The. Concept. Of. Time. The. Concept. Of. Measured. Time. More. Specifically. To. Change. The. Course. Of. The. River. Entirely. The. Only. Way. That. You're. Going. To. Know. Is. Through. The. Subtraction. Thank. You. So. Much. For. Listening. To. Today's. Episode. And. Even. If. You. Were. To. Replace. Something. In. Your. Life. How. Would. It. Change. And. This. Really. Allows. You. To. Choose. Your. Activities. A. Little. Bit. Rise. For. Your. Life. And. You. Are. A.! If. You. Have. Found. This. Valuable. And. You. Want. To. Give. Back. There. Is. A. Simple. Way. You. Can. Do. That. If. You. Go. And. Subscribe. Rate. And. Review. The. Best. Way. To. Help. Developers. Get. In. Front. Of. The. Eyes. Of. Those. Other. Developers. Thank. You. So. Much. For. Listening. To. Today's. Episode. And. Until. Next. Time. Enjoy. Your. Life. And. Be.! Happy.