CoRecursive: Coding Stories - Story - Code as a Lifeline: Brain Injury Sparks Python Mastery

Episode Date: January 2, 2024

What if your dreams were suddenly ripped away? What if your talents vanished, your passions erased? That's what happened to Jason McDonald when a traumatic brain injury at 16 ravaged his planned destiny of becoming a doctor. Jason painfully rebuilt his ind and body from scratch - relearning to read, write, even speak.   A serendipitous discovery of coding ignited a new passion within Jason. He dove into the world of Python, even writing a popular programming book. His is a story of the incredible resilience of the human spirit when faced with life-altering challenges. One that calls us to embrace our own vulnerabilities as gateways to growth. Episode Page Support The Show Subscribe To The Podcast Join The Newsletter  

Hi, this is Co-Recursive, and I'm Adam Gordon-Bell. Each episode is the story of a piece of software being built. Today's story actually is not a piece of software being built. It's the story about Jason McDonald and his unique path to becoming a software developer. It's a story about adversity. It's a story about Jason McDonald and his unique path to becoming a software developer. It's a story about adversity. It's a story about change. It's a weird thing for your first full-time job to be as a senior engineer. I'm dealing with massive life changes, moving cross-country.

I'm dealing with, you know, the lingering effects of the anxiety. That's just, that's weird. That's not a normal, that's not a normal, that's not a normal career progression, certainly. Jason wrote a great book on Python development. And Jason also trained many people to code. He's a great teacher. He's a great organizer of projects. But yeah, today we are talking about Jason's challenges managing his own brain. Today we're talking about the struggles

he had managing cognitive energy. Unless you figure out how to address it, pay it down, and stop accruing more energy debt, you're just going to continue to descend into discontentment and exhaustion. And at some point, you're literally just going to run out of all enthusiasm for life altogether. And that leads to depression. It leads to anxiety. Unchecked can even lead to suicide. You know, dealing with burnout, dealing with stress, I think those are things we all face at times, but also something unique, something that I hope you never have to deal with, recovering from a traumatic brain injury. struggle just doing simple things you used to be able to do is like climbing a mountain you know you're in a world where everything just leads to frustration where conversations drain you

where your your brain isn't working well how will you get back to the function that you know that you used to have that's jason's story that we're going to cover. And also coming out the other side of it, maybe as a better person, maybe with a better understanding of how your brain works. Let's start at the beginning, back when Jason McDonald was certain of one thing,

that he was going to be a doctor. That was my goal. I wanted to be a doctor. Specifically in the words of a five-year-old me, I want to be a pediatric plumber surgeon. Everyone would laugh at that coming from a five-year-old, but I was dead serious. I collected medical textbooks. I owned a copy of Grey's Anatomy at age eight. Grey's Anatomy, in case anyone's wondering, it's not the TV show, it's the medical textbook, which the TV show was named after. I owned the textbook. I spent hours going through those because it just fascinated me.

I wanted to be a doctor. By the time Jason was in high school, he was ahead of the curve. He was homeschooled by his mom. He was acing biology. He was devouring book after book. And he got his sights set. He was laser focused on being a doctor.

But life, as it often does, it threw him a curveball. And at 16, Jason takes a bad tumble down the stairs. Hit my head on the banister. And basically, the right side of my brain was injured. And I went from a 4.0 sophomore, college-level reading, to failing pre-K material. All of a sudden, Jason's life was different. You're trying to do things that should be easy. And at least you think they should be easy.

They used to be easy. And now it just requires all of this energy. Just having a simple conversation now takes the same amount of energy as solving a quadratic equation in your head. It hurts. You've got a headache. You're tired. It's like, why is this so hard? All I want to do is tell someone what I want to have for lunch. Why is this so difficult? A lot of traumatic brain injury survivors struggle with this. You need to use all your concentration just to do basic life functions. And that doesn't leave a lot left over for, you know, more advanced things.

And so you're just, you're tired. And with tiredness comes just crankiness. And one gets really cranky after a head injury, like just really grumpy. It's not because we don't appreciate the people around us, but we're just tired. We're just tired of trying to make our brain work. It's like, why can't I remember something simple? Or why can't I do this basic thing? And you begin to feel defective.

And it's not a defect. It's no different than a broken leg in that you just got to stay off it for a while and then work for the physical therapy. But it's a long and annoying process. And it's not like you can stay off your brain. That's the other part of it. You have to think to live. So it's like having to walk on the leg constantly and it hurts. So here Jason is 16 and all of a sudden he needs to start relearning everything. Needs to relearn reading and writing, but also more basic things like communicating. And doctors tell his mom that the key to getting this all to work is fine motor skills. I did needlepoint for an hour and then I was able to read two words. This is something.

So I was doing needlepoint. I was doing cross stitch. I was sculpting with clay. I was making models. Anything I could do with my hands that involved like fine articulated work so that was difficult talking backwards frequently was hard talking backwards was frequently hard well there you go it still happens to me now i would often say things backwards i would have the words like even right there i'd have the words and then i would mix them up inadvertently and it was a lot worse then like i tried to say something it just wasn't wasn't in order it didn't make sense i would get frustrated because i get blank stares from people i'm just like how do you not understand me it wasn't them it was just i couldn't figure how to get things

out straight it still happens now in them but nowhere near as much as it used to. Jason's world transformed from being fixated on the path to becoming a doctor to, you know, focusing in on activities that used his hands. These activities became his therapy, helping him reclaim some of what was taken from him. We had to, we had to do a lot more needlepoint, a lot more sculpting, a lot more fine motor skills. I tried to do a little bit of that schoolwork. And then when I'd get tired, take a break, maybe take a nap. Took a lot of naps after the TBI. The whole thing was a frustrating process. Not only was Jason lacking the skills he had before, but also the simplest of things could wear him out. Jason's mom started looking for experts to help, and they ended up at the Seattle Children's Hospital.

I'm not sure the guy actually believed me, first of all. But I still remember sitting in his office and him saying, well, whatever deficit you think you have, you're just going to have to live with. So if it's really so bad, give up on college. And he walks out. And I wanted to die. I was like, how am I supposed to function like this? Especially if no one's going to believe me. I have a trained medical professional telling me, this is your life. Get used to it.

And this is one of the reasons why the suicide rate is so high among TBI survivors. It's because there are a lot of medical professionals who will say things like that. They don't believe that what you're going through is real. Or if it is real, it's just, you're just going to have to learn to live with it. And it's not their brain, it's not their body. So they just have this abhorrent lack of empathy. But my mother, God bless her, did not accept that as the final answer. She was a med tech in the Air Force. She's like, no, I know it's possible to recover from a TBI.

That there, what he just said is a lie. She made a deployment with a neuropsychologist, Dr. Sharon Ashman, also at Seattle Children's. And Sharon and her team spent like three hours assessing me. And her verdict at the end of it is, you know what? You used to be here. We're going to do everything in our power to get you as close to where you were as we can. We're not accepting the current state of things as final. What Dr. Sharon Ashman said was even people who are quite old and who've had a stroke,

if they can put in the work, right, they can recover some function. But she's like, we're not dealing with a 70-year-old brain. We're dealing with a 16-year-old brain. It's still forming. We can do something with this. And so she made it her goal to get me as close to what used to be my normal as she could. And so between her team and my mom and my teachers at Columbia virtual Academy, who were advising my homeschooling curriculum, we worked out just this fairly complex program of the fine motor skills and the academic

curriculum and the coping mechanisms and the counseling and all the things I needed to be able to recover. All of the intellectual things aside of, here's how we fix this practically. The first thing and the most, I would say the most important thing she did was hope. Because without hope, nothing else would work. And so began two horrible years of Jason's life, the rebuilding years. It's like trying to lift your arm because you know you can lift your arm and yet no matter how hard you try, you can't lift it. It's one of the most frustrating feelings in the world because you know it's there.

It's attached to you. You can't make it work except instead of your arm, it's your thoughts. I was a voracious reader. I enjoyed, I've always enjoyed reading fiction. Kind of just had to set reading aside for a while. I just, I couldn't, I couldn't make sense of what was on the page. Even, even, even like picture books, just too, too hard. I couldn't figure sense of what was on the page. Even like picture books, just too hard. I couldn't figure out what it said.

And it's not that I forgot the mechanics of learning. It's that my brain was not able to process what was there. You're just like, why can't I connect these two things? Looking at a page of written words, knowing I should be able to read this, and yet not being able to make heads or tails of the squiggles on the page is an absolutely terrifying feeling. Not everyone got what Jason was dealing with. His grandparents just wanted him to shake it off, to go back to being normal. They didn't really believe him.

Finally, I wound up saying, you know what? I don't need you in my life. If this is the influence you're going to be in my life, you've had a few years to figure this out. If this is the influence you're going to be in my life, constantly criticizing the fact that I'm not where you think I should be yet, then there needs to be some distance there. I love you. I forgive you.

But that does not mean I need to keep you in my life. But over time, Jason got better at explaining what was going on for those who haven't experienced it. He said it's sort of like being locked out of your house while renovations happen. And by the time you finally fight your way past the barricade into your house, they have finished and they have completely renovated your entire house. And nothing is where it was supposed to be. You walk in the kitchen, it is now the bedroom.

You walk into the bathroom, it's the back porch. And nothing is where you remember it. You're finding things that are broken and missing. And if you just focus on that part, it's going to drive you crazy. What I had to do was focus on the things that weren't there before that are now there. You go into what used to be the storage room, and you know how the music conservatory. It's like, where did this come from? Strangely, the thing that

really helped Jason come to terms with this all is the British TV show Doctor Who. Doctor Who is a low-budget BBC sci-fi that achieved a cult following on the basis that it just had a really creative plot. So it's been

running on and off since I believe the 1960s. And the basic premise of the show is that it follows an alien who calls himself the Doctor. And he looks human, but he is actually from the planet Gallifrey. He's a Time Lord. And Time Lords have a few little tricks up their sleeve. One of which is that when they are mortally wounded, they are able to regenerate, which is a little bit like how Phoenix regenerates, Flame and whatever. But

when they regenerate, they change their face, they change their personality. But it's still them underneath. It's still them. It's just they look very different. They act very different. But it's just kind of a different reflection of who they are. And that's also the reason why I use the analogy of Doctor Who is the Doctor always has to learn who they are now. And has to figure out, like the Tenth Doctor once said, I don't know what kind of man I am now. Am I grumpy?

Am I jovial? Am I cranky? Am I fast? Am I slow? Am I brilliant? Am I stupid? I don't know. I don't know.

I have to figure that out. And that's what it's like after TBI. You don't know what kind of person you are anymore. And so it becomes kind of that process of relearning who you are and then focusing on what can I do now that I couldn't do before. So Jason has done a lot of recovery now. He's a new reborn Doctor Who, and he's trying to figure out what type of person he is. And then he finds something. So before the head injury, I had tried to code. I had tried software engineering. I tried them because I'd wanted to make educational games.

That was kind of a hobby because I'd played them so much. I have a huge collection of 1990s learning company and broader band games. Karma San Diego is my all-time favorite. I have played through Great Chase Through Time at least 50 times. I love that game. So at one point, I tried to learn Python, and it just did not make sense. I was going through it going, this is just, it made about as much sense as math did to me. I could figure this out, but this is really, I feel like I'm taking my teeth out with a spoon. This is not fun. I don't want to do this. So I set it aside and swore I would never code. But then Jason had the head injury and part of his recovery process was going back to those same educational games. And after about two years, he was back doing his high school level material.

Sure. Exhaustion was still a factor, but he's nearing the end of his high school curriculum. I thought, you know, I'd like to make a game. That'd be cool. That'd be a cool senior project. Let's make a game. But I couldn't find game-making software that would do what I want. And mom's like, well, maybe you should just code it yourself.

I'm like, people with college degrees code. I mean, like, you have to go to college to learn it. This is for, like, super smart people. I can't code, mom. I'm like, people with college degrees code. I mean, like you have to go to college to learn it. This is for like super smart people. I can't code. And I'm like, I think you could. So she bought me Sam's Learn Visual Basic.net in 24 hours. And she said, let's just do this together. Just try it out. And then when we get through the whole book, if you still don't want to code, you don't have to code. This is part of your schoolwork now. One of the first things that Jason learned in that book is how to make a Windows dialog box. If you know vb.net, it's got this design surface, and you know, you can drag a button, add it, and then click on the button and

add the code behind. You could set the size of the button through the UI or the color of the text. It's exciting. There's excitement. You know, the first time you run your program and it pops up with that button you added with that message that you put there. Exactly. Yeah, that was the moment I was hooked was the first time I created a dialog box and it pops up, says, hello world. I'm like, I did something.

Those dialog boxes have been seeing my entire time using computers with the okay button that is not just any okay button that's my okay button i made that and that that feeling of raw power in my hand i can make anything was just exhilarating and i i was hooked and it was because of the traumatic brain injury that math and computer science and and and the sort of logical empirical things just made sense to me where biology had used to make sense now math made sense instead and i fell in love with coding and couldn't get enough. I taught myself from that one book. I went from there and I learned the right... Actually, I still have it.

I still have Visual Basic 2010 sitting on my shelf behind me there. I picked up that book and just chewed through it and learned all these different techniques. Couldn't have done that without the head injury. Here's the interesting part. Coding with Jason's new brain, it didn't wear him out. You know, it didn't drain him like some other activities that seemed to energize him. And so he kept at it. And at some point he moved past.NET for his game engine. He switched to C++. He switched to Python. And meanwhile, in his previous life, Jason knew all about IRC because his mom had run an IRC-based writing workshop back when he was a kid.

So my first instinct when I was looking through how do you get help about Python, I'd see IRC and I'm like, there you go. I picked up Python in the summer of 2011 and logged into the chat room because I couldn't figure out how to instantiate a data type. I've been working with Visual Basic up to that point. Everything was in data types to me. So I log in and I say, how do you define a data type on a variable? And I still remember the first IRC response I ever got was, you're a data type and uh for some reason at that point I fell in love

with Python because just sort of that snarky irreverent pedantic sort of approach to things just kind of spoke to my heart and the person who said that he was not being unkind his screen name is Habnabbit and um he's on the Python IRC channel he's a perennial there and he went on to explain very very adeptly that uh oh you don't need to declare data types in python it figures it out from the data you pass it really wow this is like magic it was it took me it took me a while to get my head wrapped around that paradigm but i i stayed in that irc room and i basically lived there for a few years with just like absorbing everything i possibly could for the conversations so i learned tkinter gui framework and then i started learning wx widgets and then i started learning the the cute library and along the way i'm building like because i

learned by building so i'm building all these little applications or whatever as I go, just these small projects, just a few of them are still floating around out there, actually. Although they shall remain unnamed because, frankly, I think several of them need to be shot. So through all this, Jason's at university. He starts in computer science. He switches to communications. He has ups and he has downs. But his real love is the coding.

He's diving into C++. He's diving into Python. He's hanging out on the Python IRC. And most importantly, he's just building stuff. But his past.NET experience and his kind of unique learning style made some things difficult. I had learned the empirically right way of doing things in.NET, in Visual Basic. So I kept trying to apply those patterns to Python because it's what I knew. And I knew it wasn't the right way of doing it,

but I couldn't figure out the way I was supposed to do it just from looking at the source code. And Python has a lot of things, but their documentation is not particularly insightful if you're trying to pick it up from another language. You have to know what you're looking for. And to make sense of the Python documentation, you almost have to know Python. At the same time, I'm noticing in IRC

that the same questions keep being asked over and over and over. People keep asking the same things. And I was learning a lot of my stuff about Python from what people were asking. So Jason starts tracking the things people are asking for in IRC and compiling his own version of an FAQ. He publishes it as a series on Dev2. That's dev.to if you're not familiar. I just thought, well, I'll just put it out there.

Someone will find it. Maybe I can start throwing these links in IR feed. And then I have a friend of mine message me one day. And he says, have you seen the Google News feed? I said, no, I don't follow the Google News feed. He said, you're in it. My article had actually hit trending. One of my Dead Simple Python articles had actually started trending.

It was on the Google News feed as have you missed this yet? I'm like, are you serious? So I began to realize I had written something that was actually providing a lot of value. Jason was already writing technical content at this point. He had even talked to an editor about possibly writing a C++ book. This editor, who shall remain nameless, he sees this article series. He goes, by the way, you could make a book out of that. I'm like, I guess I could. I hadn't thought of it.

It had never occurred to me before that it was worthy of publication outside of the internet. So I wind up dropping a note to No Starch Press. Because I own with No Starch Press books. I love the publishers. I'm like, I should do that. So I drop a note to No Storage Press. I'm like, hey, is this something that you would, not 24 hours later,

hear back from one of their editors. Yes, let's do this. This is perfect. I went up on a phone call with Bill Pollack that same week. And he's like, yeah, I'm looking at this article. This is great.

This is exactly the sort of material we need. I have not seen a Python book like this because it wasn't a python book for someone who never coded before it was a python book for someone who knew how to code and just didn't know python it was that that gap so i began writing that book and i found the guys in irc who always argued with me every time i try to answer a question they come along and go well technically and make some sort of really pedantic correction that will almost just really annoy you and i said hey will you edit my book because i know if you guys edit it it's going to be correct because they didn't even agree with each other so i became a python expert in the course of writing this i went from being a halfway decent python coder to a Python expert in the course of writing this. I went from being a halfway

decent Python coder to being an expert in the language just because I had to research and write all of these really fiddly examples. Writing examples is hard. From writing my own tutorials, I've learned that you don't always want an expert teaching you. An expert can be out of touch with the problems that new learners have. That was not Jason's problem. I had never lost touch with the frustrating period of trying to learn coding or trying to learn Python. I once spent an entire day just trying to figure out how to run a Python program. Because believe it or not, nobody wrote that down. Search the internet. You will not find a tutorial that says, here's how you run a Python program. Because believe it or not, nobody wrote that down. Search the internet.

You will not find a tutorial that says, here's how you run a Python program. Everyone tells you how to run a single file, but they tend to skip over what you do when you get to multiple files. I'm like, all right, chapter two. Here's how you run Python code. Because no one had ever told me. I had to figure it out by asking the IRC room, like, how am I supposed

to run this? They're like, you don't know? No, I've never used Python before. How do you run the code? Python space dash m space the name of the directory containing your code which should have a dunder init dot py file and all of the other files and then you also need to have an

entry point here to find this thanks why has no one ever written this down it's well i guess we just never thought of it i remember what it was like to not understand so it gave me the empathy i guess is what it comes down to it gave me the empathy to think oh maybe this isn't so obvious maybe someone needs to write this down so they don't have to struggle where I struggle. Because that's a weird thing about our society, isn't it? A lot of people, when they struggle, they feel like it is now their right

to cause other people to struggle in the same way they did. Well, I, quote, earned my stripes, and so you have to as well. And I think there's almost something a little nefarious about it. I had to deal with a boot in my neck for five years, and I just comforted myself by telling myself, it'll be my turn to put my boot in someone else's neck eventually, and you're not going to take that away from me. It's, oh, just don't perpetrate a cycle. So Jason spends tons of time writing his Python book, years really, and he learns a lot from it, and not just about Python. This has definitely underscored this concept for me that we often frame things like dyslexia, like ADHD, like autism, like Tourette's, traumatic brain injuries.

We frame these as disabilities. That's the word we use, disability. That's what it's legally defined as. That's what all the legislation is called. That's what your HR department is going to call it. That's what your we use, disability. That's what it's legally defined as. That's what all the legislation is called. That's what your HR department is going to call it. Your doc is going to call it, but it's a bit of a misnomer because every brain has its challenges. Our society is tuned to compensate for and hide one set of challenges. What we refer to as a neuronal person. Now, by the way, you've never actually met anyone who's normal because neuronal was just kind of the average of the trends.

And so this is that middle of the bell curve for everything composite into one person. That's a normal person. You've never met one. No one's there. There are people who are more towards the middle of that. And society's tuned to kind of hide the challenges that they have. It's true, right? A society where most people were blind would be set up to serve the

majority blind people, which would mean it would be very supportive and necessarily mask some of the sight deficits. Jason says it's the same for our current world. It's masking the deficits of the people that we consider normal. When somebody is missing or has something different than the majority, then that's when it stands out. And we label that as a disability. What I've learned to see it as, what I've helped other people to see it as, is actually a superpower. Every one of these brainwirings I described has unique strengths. They have unique weaknesses and they have unique strengths. A normal brain has unique strengths and unique weaknesses as well. Learning to live with it is not just a matter of accepting I am broken. In fact, broken is the wrong perspective. I'm not broken. I'm different. I could write Dead Simple Python because of the TBI, not in spite of it, because of it. If I hadn't had the TBI, that book would not exist. So it was learning that your

unique brain has a superpower. It has an ability that most people don't have. Recognizing that, learning to capitalize on that, but then also learning that that superpower brings with it the ability to overcome your challenges. So you learn to use your strengths to overcome your weaknesses. So Jason toiled away on the book and after university, he started job hunting, but his uniqueness caused some trouble. His resume is not typical, and he sometimes hit snags during the interview process. who had interviewed me were ecstatic they're like oh my gosh she said oh we're we're gonna recommend the way how are you this is this is you you you're gonna be such a great fit for this team we're so excited by the way he's he he's written books too oh my gosh you guys are just gonna hit

it off this is gonna be great and you can help with this and they're going on about about imagining what it's gonna be like having me on the team and they're ecstatic and they're excited. And then the next day I get the call back from the HR person who's coordinating the interviews. And she said, oh, we decided not to move forward with your application. The technical team felt that you don't have enough experience. I'm like, no, they didn't say that. Someone else put the kibosh on it. And I genuinely believe it was because of my background. I knew everything they wanted me to know. I went right down the checklist. I proved it.

I passed the technical interview. I answered every question, solved every coding challenge. They were excited to bring me on. A person who had never spoken to me had simply decided they didn't want me. What Jason figures is that someone saw his resume, someone who didn't get a chance to meet him, and felt like, hey, this guy's not right for the job. He's not one of us. He's another. All othering really is. Othering is where you say, you're not part of my group. You're part of the other group. Whether it's an identity crisis or an unwillingness to recognize privilege, they have to find something that says, I am worthy of this. So they pick whatever it is. I'm college educated. I'm white. I'm middle class. I'm American. I am a C++ developer. I code in Vim. I, whatever it is. And then they decide from there, if that is what makes me special, then if you don't have

it, you're not special. So now they have to attack. They have to denigrate. They have to gatekeep. They can't let them into the room. They can't give them a chance because if the other group gets in the room and proves they're every bit as smart, then that ruins the narrative. So they have to keep them out. That's all gatekeeping is. So Jason's trying to find work and he's

getting a lot of rejections and that can take its toll. Along the way, he starts having panic attacks. Then he gets diagnosed as having an anxiety disorder. And then something in his personal life happens, something that we discuss, but he doesn't want to talk about. But I'll just say it's something that's really, really traumatic, something that you wouldn't wish on anyone. And that traumatic event makes him feel unsafe on like a moment-to-moment basis. And things really start to spiral spiral so if you've never had

an anxiety disorder then imagine if you're watching like an exciting riskery movie and the moment where the monster pops up and that feel initial feeling like where your brain is going do i attack do i run away or do i just freeze and hope it doesn't see me? Now take that moment, that second in time for a normal panic attack. You say that out for five minutes, it just doesn't go away. And so you're, you're paralyzed because you're trying to process this and, and everything suddenly feels terrifying, like a threat. You don't feel safe. You feel you're anxious. You're tense. You're ready to jump out the nearest window to survive. That sort of feeling, but over something that isn't the monster jumping out from behind the couch. But from not remembering the combination for your locker.

That's a panic attack. So imagine being in that wound up state where it's hard to breathe. Like your heart is racing and you're just, you can't. It's just, oh, imagine that for three months. Prolonged stress, severe emotional trauma, they can injure your brain just like a blow to the head. You know, think of victims of PTSD and the challenges that they face.

Jason going through this experience, he feels changed and more and more, he doesn't really recognize himself, but he does find a job. He gets a job working for Canonical. It's a great company. And he moves cross country to take it. It's a weird thing for your first full-time job to be as a senior engineer. That's weird. That's not a normal career progression, certainly. So I'm dealing with massive life changes. I'm dealing with moving cross-country.

I'm dealing with the lingering effects of the anxiety, all these things. I can't sort out why I keep burning out we ship the ubuntu operating system to the cloud providers if something breaks you've got to figure that out yesterday and so it was it was a lot of a lot of hurried debugging with with limited insights into what what was broken not a great fit for me i did i, I did well enough at it, but it just can sell a wound up switching to finding a coding job, switching to that. My, my boss,

Eric at, at canonical was very supportive. He said, you're a, you do great at this job, but I can see the job is not great for you. So he was very, very,

um, supportive of my, of my finding somewhere that, that, that would work for me. Jason love coding, right? Like the excitement of it sustained him through so much.

But now something had changed. Something's wrong. It's not clicking anymore. I can do it. I can do it really well. No one can argue with my technical ability, but why am I not enjoying it anymore? Why am I exhausted at the end of every workday?

It wasn't until I was working on this one project where I had struggled for two hours to solve a bug and I solved it and it worked. And instead of getting that moment of, yes, I solved it, I'm brilliant. What I got instead was that so wasn't worth two hours. And I just sat there, I wanted to cry. I'm like, this is why I keep

burning out. I haven't felt that exhilaration of I solved it since 2018. And that's when I realized I don't like coding anymore. It's not that I can't do it. It's not even that I don't prefer it. It's the fact that it takes more energy now. And so I might be using all of my survival energy just to code. And then I can't even make a simple meal. This is basically burnout, right? This is the world grinding you down. But Jason, because of his time from 16 to 18, because of his time he spent recovering, he's tuned into this process, right? He had days before where just doing some basic needlepoint, doing some learning games would exhaust him. And so he recognizes this feeling. He understands what's happening because he's been here before.

But the problem is the thing that once gave him strength, the thing that helped him in the past is now the very thing that's wearing him down. The thing that helped him in the past is now the very thing that's wearing him down. The thing to remember is that there is an actual scientifically measurable upper limit to how much cognitive energy you have a day. It is a function of your metabolism and several other factors. Your brain can actually only do so much. It's almost like a capacity on a generator. Once you exceed that capacity, the generator circuits are going to blow every single time. It doesn't matter what you do. You can't exceed a certain capacity. When you are not aligned with your passions and your strengths, it's going to take a lot more cognitive energy

to do that task. Now, we all have things that we don't like. We all have things that we have to do that don't align with our strengths. I'm not a fan of washing dishes, but I do it every day. But the more time you spend doing something that you just don't have a passion for, the more energy you're using. And if you remember that you have a finite amount of energy, you're using up energy that you could be using for other things and need to be using for other things. So you're not just taking away from your emotional contentment. You're actually taking away from the energy you need to survive. This is why a lot of people come home, fall on the couch and binge watch Netflix because they are just out of energy.

The brain is out of gas and goes, I can do nothing else. And that leads to higher stress and higher stress leads to health problems. It reduces your quality of life. It negatively impacts your relationships. It's going to affect everybody around you when you're out of energy. Jason says, though, there is a way out of burnout. It's our job to recognize where we are passionate and where we are skilled and where we're not. And to start that conversation, we have to leave that conversation to even the best employer.

We're still just names in an HR system. We're still just numbers on a spreadsheet. They don't know us as people a lot of the time. Even the best companies don't have a magic lens to see inside of our brains. So giving ourselves grace and recognizing that the fact we're burning out is not because we're bad we're not broken we're not defective we're just different everybody's different everyone struggles everyone has something in their life that doesn't make sense the question isn't really whether or not we've struggled the question is whether or not we are willing to admit it, willing to remember it.

And then it's also a matter of if we're willing to then apply it to other situations. And so Jason starts examining himself. He starts reflecting on his work and on his energy levels. What are all the moments in my career or in my life that I feel alive, happy? And I thought, well, it was the time I organized that one project that was overdue and the project manager

had been left out of the loop on everything and so didn't have the context to catch up. I got that project done. That felt good. Organizing six different teams and getting that done was amazing. There was a time I got that project done. That felt good. Organizing six different teams and getting that done was amazing. There was a time I wrote that policy document and we implemented it on the team and our quality and our response times got way better. What do you look forward to when you get that email that says, could you do X and you get excited? What is that? Figure that out because we all have that write your own ideal job description

and then work with your supervisor work with your manager to say i'm noticing that i'm struggling in this area i can do it but i'm exhausted afterward but where i am invigorated is when i'm able to do this and this and this and this and this a good manager, a good supervisor will go, okay, note it. Let's see if we can move it. And it takes time. It's not an instant thing. But a good manager will help steer you in the direction of your strengths. And as I started looking and I went, wait a minute, what I'm doing is no longer software engineering.

I'm a business analyst. I'm a software engineering manager. I'm a project manager. I'm a software engineering manager. I'm a project manager. I'm a facilitator. That's what I like. And once I realized that, I started rearranging my role in different projects and I started putting myself where I was doing more facilitation than coding. And the burnout started resolving. And I started finding that I was enjoying going to work and I was enjoying doing things and my productivity was going up and I had energy for other things. So now Jason knows himself, right? He's recovered. He's on the mend. He knows his strengths.

He knows what energizes him and he knows what wears him down. And you know what? He made it through this burnout using the skills he learned recovering from a brain injury. Those tools, that self-awareness, they might have been what saved him here. Which brings to mind an interesting question. So a lot of people have asked me, would you change your TBI if you could? I'm like, no, no, actually I wouldn't. Because a version of me between age two and age 16 could not have done what I did. Did not have that personality. There are, there are skills and abilities that I gained as a result of that TBI that I would never have had. Sure. Maybe I would

have saved some lives, but you know what? I would have been arrogant. I would have been insufferable. I don't think I would have been the sort of person that I would have been insufferable. I don't think I would have been the sort of person that I would have wanted to be around now. And I wouldn't trade this because, yeah, the things I found in that remodeled house are far better than the things I had before. Jason found out who he was again. And for me, it draws attention to the fact that we're always

changing, right? We all become different people. I haven't been through what he's been through, but I have over the course of my life, lost abilities, gained new ones, things I loved that I don't like anymore, and new things that excite me. Part of life is changing, right? And for Jason, things kept changing. He lost his job in the recent tech layoffs, and now he's job hunting again. But not for a programming job. That's his previous incarnation, right? He's different now. He's now energized by leading teams and managing projects. So if you're hiring, look him up. And if you want to learn Python, check out his book. It's still a fantastic book.

And even though Jason's different now, he still loves the zen of Python. Beautiful is better than ugly. Explicit is better than implicit. Simple is better than complex. Complex is better than complicated. Flat is better than nested. Sparse is better than complex. Complex is better than complicated. Flat is better than nested. Sparse is better than dense. Readability counts.

Special cases aren't special enough to break the rules, although practicality beats purity. Errors should never pass silently unless explicitly silenced. In the face of ambiguity, refuse the temptation to guess. There should be one, and preferably only one, obvious way to do it. Although that way may not be obvious at first, unless you're Dutch. Now is better than never, although never is often better than right now. If the implementation is hard to explain, it may be a bad idea. If the implementation is easy to explain, it may be a good idea. Namespaces are one honking great idea. Let's do more of those.

That's the episode. And if you like the sound of that, you might like Jason's book, Dead Simple Python. Also, check out the Code Recursive newsletter. It comes out monthly. I'll tell you some behind the scenes about the latest episodes. And I'd like to say thank you so much to the people who support the podcast. If you want to support it, you can to co-recursive.com slash supporters and you know donate some monthly money and that helps me keep going and helps me justify it to my wife all the

time i spend talking into this microphone and interviewing people so thank you so much to everybody who supports the podcast and until next time thank you so much for listening.