Have you ever felt stuck? I don't mean stuck on a problem, like you can't solve it. I mean, stuck is if you're not progressing, things have slowed down. It's not like things are going poorly, necessarily, but you don't seem to be progressing very quickly in your career or your relationships. We're going to talk about one reason why that might be in today's episode. My name is Jonathan Cutrell, you're listening to Developer Tea. My goal on this show is to help driven developers like you find clarity, perspective, and purpose in their careers. Much of the time when we feel stuck, we have some level of influence both over this feeling and over our situation. We can recognize the feeling as just one of the experiences of life. It's easy to dismiss this if that's your goal. But I suspect that if you are feeling this, it's because you've observed something about your career that's unsettling. Something isn't moving the way that you thought it would. I want you to be very specific if you're going to engage with this episode. I want you to be very specific, very explicit about what that thing is. What is it that you thought would move along differently than it's currently moving along? For example, is it your pay? Or maybe it's the feeling that you have when you're around other engineers. You don't feel like you can connect with them on a technical level. Or maybe it has nothing to do with these things at all. Whatever it is, be very explicitly clear about what you feel stalled out on. In today's episode, I want to introduce an idea, kind of a mental model that I'm going to call the bowl of mediocrity. We're going to talk about the bowl of mediocrity. What have we talked about today's sponsor? Today's episode is sponsored by Command Line Heroes. Season 7 of Command Line Heroes is available now. I can tell you right now, if you're somewhere around my age, you're going to find it very nostalgic, but also an incredible dive into the history of what got us where we are today. Many of us as software engineers, we depend on the things that are talked about in this season. We go back to a pivotal year, 1995, the start of the dot com boom. But it didn't just happen automatically. A lot of things had to come together for the internet to succeed. For example, back then, GoDaddy didn't exist. What did you do to find a domain? Well, as it turns out, there was a woman that you'd have to call, her name was Elizabeth Jake Feinler, and she was the keeper of all domains. This and many other kind of wild pieces of lore about how the internet came to be can be found on season 7 of Command Line Heroes. Command Line Heroes is hosted by developer and podcasters Ron Yutbark. Go and check it out wherever you listen to pod casts. I've had a chance to get into this podcast and it does feel like I'm listening almost to a choose your own adventure kind of documentary mashup with real life. It's really cool. You can find command line heroes wherever you listen to podcasts. My thanks to command line heroes for their support of Developer Tea. So we're talking today about the bowl of mediocrity. You might find yourself in this bowl. When we're talking about this, I want you to visualize that shape of a bowl and think about it from a 2D perspective. You recut the bowl in half and you're looking at it from the side, the shape of the curve that goes down and back up. I want you to think about this as a curve on a graph, on this graph, on the y axis is effective or important. These are the higher you go on this y axis, the better off you likely are. And then on the left to right axis, you're looking at risk level. Risk level, roughly equating in this case, to difficulty or experience, things that you have experience with. The things further to the left on the x axis, you have more experience with things further to the right you are more kind of relatively inexperienced with. And you can kind of draw this out for yourself if you need a visual kind of the bowl of mediocrity. You can put it in your notebook to remind you of these things. And here's the basic idea, as people progress through their careers. Most of the time, we start out on the far left of this bowl. We don't really know a lot, but we start learning the things that are considered kind of the fundamentals, the basics. The basics of being a software engineer, the basics of working on a team, you know, the kind of basics of our, you know, the company that we're working for, whatever the business structure is, those are considered kind of the basic building blocks of a career and of a specific position. You probably have a list of these things. You could write it down pretty quickly, both that are relative to your career in general, but also to your specific business that you work in. And then all the way on the right side of this, we have things that are highly prone to failure, things that if you were to try them, you're as likely or perhaps even more likely to fail than you are to succeed. Now this graph kind of starts out with that space, you know, the full distance of that X axis is very small. As beginners, we're likely to fail at some of the most basic things. So we learn a lot in those early days because as we learn those basic things and we fail with those basic things, that X axis begins to grow. And so now we become more solid, kind of more solidified in the basic things. We begin to traverse that X axis from the left to the right. We start to learn more advanced techniques. Now here's where we make a critical error. As we learn more advanced techniques, we begin to walk away from the basics, but we don't go all the way to the right side of that X axis. In other words, we're staying in some safe space. We're trying to avoid failure by staying in the middle. This is the bowl of mediocrity. We've walked away from focusing and investing in the basics and the fundamentals, but we're not walking all the way over and attempting things that we're likely to fail at. As we are very often saying on this podcast, failure is highly correlated with learning. You don't always learn when you fail. There are some failures that seem to be random. Sometimes we don't get a lot out of them, but a lot of our learning does come along with failure. Those things tend to coincide. Interestingly, as we begin to progress in our careers and we walk away from the fundamentals, we also tend to lose touch. We don't build intuition for those fundamentals. We lose touch with them and we end up working on things that live in that kind of no man's land, middle ground. They're not highly valuable. They're challenging enough that we're not necessarily bored, but we're not becoming very good at much. My challenge to you is to focus on two areas. The fundamentals, really getting those down to the point that you have them intuitively. You're building an intuition, you're focusing on those fundamentals and spending time in that highly risky failure zone. Working on projects that you don't necessarily even feel comfortable with the scope of, trying to learn something that requires so much more of you than you expected yourself to have. There's no specific prescription of what kinds of things fit on either end of this. Sometimes what is fundamental in one business might be a very risky thing in another business. There's no specific formula for figuring out what lands were on this continuum. This is, as we mentioned earlier, very highly personalized. Things that you may have an intuition for someone else may have zero experience with. It may be very far to the right on their graph, whereas it's very far to the left on yours. It's important to recognize that this is a very personal experience thing, but the bowl of mediocrity is intended to get you thinking about the fact that these fundamentals and building a high degree of experience and expertise with the fundamentals, almost to the point that they become automatic for you. They're so intuitive. That is the basis. That is the structure and the support that you need to do the more daring, failure-prone things. You build off of that intuitive structure. If you're sitting somewhere in the middle, in the bowl of mediocrity, if you're trying to do something that's in the middle, you likely are not relying on your intuition. That's very important to focus on. You're not relying on much of your built-in intuition, your experience. Instead, you're plugging along without really learning much at all. This is where that feeling of slowing down comes from. If I had to sum this up, refocus yourself, the first step here is refocus yourself on the fundamentals. Look for opportunities in that space. Look for opportunities that look like high-risk, high-reward scenarios. This is at a personal level. High-risk, high-reward for you. As a bonus tip, don't do this in the dark. Talk to other people in your organization, especially talk to your manager or a mentor, somebody who you can bounce these ideas off of. Let them know that you want to focus, you want to build up your expertise as a fundamental engineer, but also you want to take a shot at something that is higher on that risk profile for you. See what they say. It's very possible that you are overestimating the risk. It's also possible that you're overestimating the value of that thing. You might need to choose a different thing. Focus on the fundamentals and then bounce your ideas off. Look for opportunities to take deep shots. Don't work in that middle space. Try to avoid working in that middle space. Eventually, the things that are fundamentals, you'll begin to expand that. The bowl begins to meet in the middle. Some of the things that are currently in the middle, those will become intuitive to you as well. Very fluid graph and your goal should be to build up a very strong base so that you can take those riskier shots and become comfortable with taking risk towards failures so that you can learn more. Your learning curve is going to go through the roof if you're failing more often. Thank you so much for listening to this episode of Developer Tea. A huge thank you again back to Command Line Heroes. Season 7 of Command Line Heroes takes you back to the pivotal year of 1995. You can find that podcast anywhere you listen to podcasts. Where you're listening to this one right now. Over the course of the past year, the pandemic and very likely the fewer people actually going on their daily commute. This has had an impact on all podcasts. So we're trying to, every podcast you listen to is likely trying to find their way and reach listeners who are listening in new ways. I'd love to hear from you about how you listen to this podcast. And also, if you know somebody who's searching for a podcast, please take a moment to send this podcast to them. This is the best way you can help this show reach new engineers like you who are looking for clarity, perspective, and purpose in their careers. If you enjoyed this discussion, but you want to go deeper, you want to reflect your ideas off of other engineers. Encourage you to join the Developer Tea Discord community. Head over to developertea.com slash discord. Thanks so much for listening. And until next time, enjoy your tea.