often in our work we have to make sense of what we are seeing and making sense is something that we do quite well as humans but sometimes in the process of the sense making we cut out a lot of useful and sometimes even critical information my name is jonathan cuttrell you're listening to developer team my goal on this show is to help driven developers like you find clarity perspective and purpose in their careers i want to do a little experiment with you let's imagine that you are tasked with coming up with a list of requirements for a job position now let's imagine that as a part of this list of requirements you also need to come up with some kind of threshold that the prospective candidate needs to meet in other words some percentage if you're looking at your list of requirements that they need to meet some percentage of those requirements now let's imagine that some of the requirements are kind of considered core requirements so we'll set those aside and just look at the remainder what is the threshold that a candidate should meet in order to meet the requirements of the job position so let's imagine that as a part of this list of requirements we have a list of requirements that we need to meet in order to be considered a good candidate this is somewhat arbitrary so we'll go with something like 90 our gut tells us that if we find a candidate that could meet 90 of what we want we could probably make up the rest of that 10 the missing 10 right now we're experiencing the sense making part of our brains we're experiencing the feeling of meeting a candidate and assigning an arbitrary value of 90 good to that candidate someone who is 90 good that sounds like a success to us this is the the kind of narrative part of our brain we imagine that the number means something and that meaning is what we focus on but what if we were to look at it from a different angle with the story of a candidate and we're looking at a candidate that's going to be a good candidate for a job position story change? That's what we're going to talk about right after we talk about today's sponsor. Developer TE is proudly supported by Doppler. The scary days of configuring, managing, and sharing secrets across different teams and clouds are over. Introducing Doppler, the first universal secrets platform that enables developers to automate the pain away of managing secrets and environment files. Doppler is your team's central source of truth for secrets and app config across all environments and clouds. Whether your secrets are in Docker, AWS, Vercel, Serverless, or anywhere else, Doppler supports wherever you're working. And as your stack evolves, Doppler remains simple. More than 11,000 customers across all company sizes, from startups to enterprises, use Doppler to keep their secrets and app configuration easy. across devices, environments, and team members. Say goodbye to those .in files and set up Doppler for your team in less than four minutes. Head over to Doppler.com slash L slash Developer TE. That's Doppler, D-O-P-P-L-E-R.com slash the letter L slash Developer TE. Thanks again to Doppler for sponsoring today's episode of Developer TE. Let's take our list of requirements. The list that we kind of whittled down, and this, again, is hypothetical. I can't imagine that you would actually write down a list while you're listening to this podcast, but let's imagine that we had, let's say, 20 or 30 items on a list. And these might be specific skills or perhaps traits or experience. Uh, specific kinds of experience that you want in a candidate, whatever those things are. Let's imagine that we found a candidate who has met 90% of that. Well, specifically, what would that look like? If we play out the statistics directly, rather than trying to derive meaning from that statistic, and if instead we say, let's remove 10% of the items on this list, then take the opportunity to randomly select one out of every 10 items and remove it entirely. Another version of this might be that on every item that you see on this list, the, uh, kind of completion metric, whatever you would consider the completion metric has only reached to an average of 90% for each of those items. This creates a list of the items that we want to remove. And then we can just take the list, and click on the title, and click on the title, and click on the title, click on the title, click on the title, click on the title, click on the title, click on the title, click on the title, click on the title, click on the title, click on the title, click on the title, click on the title, click on the title, click on the title, click on the title, click on the title, click on the title, click on the title, click on the title, click on the title, click on the title, click on the title, click on the title, click on the title, click on the title, click on the title, click on the title, click on the title, click on the title, click on the title, click on the title, click on the title, click on the title, click on the title, click on the title, click on the title, click on the title, it. Interestingly, the imagination that we have when we haven't applied those statistics is very different from the actual picture, the feeling that we get from the actual picture once those statistics have been applied. And the reason for this is because our brains, when we're in sense-making mode, we fill in the gaps. In some ways, we imagine that 90% is essentially 100%. We stretch our imagination to believe that answers are complete answers, not partial answers. If I were to ask you to estimate the number of days that you or even a team member have spent in the past year, how many days have you spent in the past year? It was going to be on your A game. How often are you going to be firing on all cylinders, doing your best at your job, you know, full of energy, all of the things that would be required for you to operate at your kind of optimal capacity. If I were to ask you, how many days are you in that state? You would probably have an answer that is lower than 100%. We all have bad days and evolution. At the same time, evolution brings evolution. At the same time, Even if your day isn't bad, it may not necessarily be that 100% optimal day. And so if you were to say, let's say 70% of the time, that would probably be a high estimate even for days that you would consider yourself optimal. And let's imagine then that if you combine all the statistics together, that your kind of performance relative to what it would be if you were on top of everything all of the time is actually somewhere around 80 to 85%. This doesn't sound unreasonable, but if you were to apply this to your, let's say, capacity planning or your personal estimates for work that you're doing, you may find yourself. Feeling surprised. And the reason for this once again is because when we're talking about things from a perspective of what's reasonable to expect out of yourself, it's easy to describe those statistics void of the actual work. But when we try to apply the statistics to some expected story, some expected narrative, for example, the kind of work or the amount of work that you're going to be able to do, to get done in a given week or month. If you were to imagine that story, it's much easier to imagine feeling good and being productive 100% of the time. Rather than accepting a more realistic perspective, which shows that 80 to 85%. Part of the reason for this is probably because we don't necessarily like that story, right? We don't necessarily want to. If you're going to adopt that narrative, we want to see ourselves being successful and full of energy and, you know, operating as optimally as possible. But if we want to be accurate, if we want to imagine a more, uh, clarified picture of our reality, then we need to find a way to bridge the gap between these statistically, uh, more accurate representations of our reality and our narrative. When this is especially pronounced is when we review something that has happened in the past. It's easy to apply statistics and understand something in retrospect. It's much harder to apply statistics in order to predict something. We use sensemaking to predict and, generally speaking, statistics to understand. And when we're looking retrospectively, it's easy to describe something because all of the pieces fit in place. We can kind of see how things went and none of it seems out of place. But looking forward, it's very hard to predict. And so one of those tools that we can use alongside our sensemaking to make our sense more accurate is those applied statistics. Try to actually... Carry those statistics out through the picture that you're creating with that sensemaking process. Thanks so much for listening to today's episode of Developer Tea. Thank you again to today's sponsor, Doppler. Doppler is your final scalable solution for dealing with environment variables. And all of those secrets that you don't want leaking out through an accidental git commit. Go and check it out. Head over to Doppler.com. Slash L. Slash Developer Tea. That's D-O-P-P-L-E-R.com. Slash the letter L. Slash Developer Tea. Thanks again to Doppler. Thanks so much for listening to this episode of Developer Tea. If you enjoyed this discussion, then I encourage you to join our Discord community. It's 100% free. Come in and ask a question. This is the most important thing you can do to get a conversation rolling. Come in with the questions that you have. Even if it seems like it's a... a completely off-the-wall question, it's going to bring something to the group. And we need you to be a part of that. Go and check it out. Head over to DeveloperTea.com. Slash Discord. Thanks so much for listening. And until next time, enjoy your tea.!