Sometimes I sit and think, and sometimes I just sit

 

What I looked like several days after being hit by an SUV while riding my bicycle

I vaguely recall gingerly walking from the garage to our upstairs family room the day after I was hit by an SUV while riding my bicycle. My body was so bruised from the waist up, it hurt to move – at all. Since my left clavicle was fractured and my right shoulder was separated (though I didn’t realize it at the time), I could only lay down on my back without crying out in pain. I parked myself on the couch recliner and tried not to think of how bad everything hurt.

Since my mouth was in a state of disrepair, it hurt to eat. I was taking pain medication that generally made my stomach match the pain I felt through the rest of my upper body. I gave up on the pain meds. I tried to eat, but my appetite was lost because of the pain from eating. I lost about 15 pounds the first month.

I went to see the doctor about my wrist. He put a cast on it and told me to come back in a month. I saw my dentist and then an oral surgeon to determine how bad my mouth really was. I could tell by the looks on their faces that it wasn’t good. The oral surgeon found the fracture in my upper jaw. He and the dentist wanted to let my teeth settle for another week or two in order to see if the remaining top front teeth would survive. I was warned then that no matter what the plan of action was, it would take a while to heal and have everything back to “normal”. I had no idea how accurate those warnings were at the time.

The most painful event I remember during the first week was trying to change my shirt. Lifting my arms anywhere close to above my shoulders hurt so bad that it brought tears to my eyes. I was determined to change my own shirt. I eventually got my shirt off, but not without a frightening popping noise from one of my shoulders and a yelp followed by more tears. Regardless, I stood there proud that I did the seemingly impossible – taking off my own shirt. It was then that I determined I would wear a consistent uniform of tank tops and full zip hoodies for the foreseeable future. I expect this to become a fashion trend in Silicon Valley any day now.

The days drifted into one another. I was waiting. Waiting for my body to heal. Waiting to see how bad the damage to my mouth really was. Waiting for the day when I could walk without feeling every step sending jolts through my chest, to my shoulders, piercing my neck.

The first week was a haze. I had no expectation of when I would feel better. I only knew how awful I felt. I think it’s important to capture that here as a reminder to myself and for others who might be going through a similar situation. No big lesson other than it hurts and there’s not much you can do about it other than to be patient as you lay there hoping the pain goes away. It does – eventually.

The title of this post comes shamelessly from Courtney Barnett’s pretty fantastic album of the same title.


 

I’m capturing my journey towards recovery after being hit by an SUV while riding my bicycle on February 8th, 2014. I’ve learned quite a bit along the way and want to share those lessons. I’m not a doctor, lawyer, or any other sort of expert in this area. Any insights I provide along the way should be taken as my insights to my particular situation. In other words, seek professional counsel if you find yourself in similar circumstances. See more here.

Throwing up blood

 

I’m starting to capture my journey towards recovery after being hit by an SUV while riding my bicycle. I’ve learned quite a bit along the way. I want to share those lessons learned. I’m not a doctor, lawyer, or any other sort of expert in this area. Any insights I provide along the way should be taken as my insights to my particular situation. In other words, seek professional counsel if you find yourself in similar circumstances.

February 8, 2014. It was a normal sunny yet cool Las Vegas winter morning. I decided to go on a longer ride, take a different route than usual. Nothing crazy, just head out a different way to the usual favorite on the west side – Red Rock Canyon. I remember coming to the first stop light. It’s a long one and I realized then that I didn’t have my sunglasses. I never ride without them. I decided to make an exception. Sure, I was only about five minutes from home, but the light was going to turn green at any moment. It did and I pedaled through and kept to the right of the road. That’s about as much as I remember about riding on February 8, 2014. The next thing I remember is waking up to my name being called, “Joshua? Joshua? Can you hear us?” My eyes opened and I couldn’t make out much. I couldn’t move my head. I was strapped down, straight as a board. I answered the calls of my name. They asked me if I knew where I was. I told them I didn’t. I asked what happened, where I was. They wanted to know more about me. Did I know my full name? Did I know what city and state I lived in? Did I remember what I was last doing? I answered their questions without hesitation. I could sense some relief on their part and that gave me some comfort, immediately followed up by panic. WHERE AM I AND WHAT HAPPENED TO ME?

Continue reading

One year ago today (…or when an SUV meets a cyclist)

I was riding my bike 5 minutes from my house one year ago today when an SUV ran a stop sign and hit me. The pictures below were a couple days later. It’s the first time I’ve looked at them myself. I’ll write more about the aftermath of it all some other time. Until then…

image

image

image

image

image

Everyone is doing Agile and Lean

Agile and Lean are old news. Everyone uses and abuses the lexicons. Have a short daily meeting? Call it a daily Scrum. Trying to deliver something in a relatively short period of time? Call it a Sprint or iteration. Have a board with post-it notes in swim lanes? Kanban at your service. Writing some tests? Call it TDD. Attempt to improve a process? Continuous improvement! Use a CI server to run a job here or there? Tell the world you’re doing continuous integration. Code on production? Continuous deployment! Meanwhile, people who list experience with Agile and Lean on their resumes more often than not talk about how painful and all around chaotic it all was. The underlying reason for this bad aftertaste is most often due to the adoption of practices without an understanding of the principles behind them.

The temptation is to read an article, watch a short video, attend a conference session and latch onto a particular Agile or Lean practice without the fuller context. This is especially popular in tech where many (most?) of us have a natural tendency to chase after shiny new objects. Instead of a collection of tools that serve their purpose within a greater context, we latch onto the hammer and start pounding everything in sight. A team struggling on a project decides to try a daily standup because they like that part of Scrum. They don’t realize the nuances behind a daily Scrum. They don’t grasp the commitment demanded by Scrum as a whole, and how the daily Scrum helps enforce that commitment. A standup is easy; building teams dedicated to consistently delivering something tangible in a short period of time is not. Every ceremony within Scrum is there because the principles drive it. Adopt one ceremony out of context and the result is less than satisfying – far short of transformative. Ditto for Lean. The practices are easy to grasp and implement poorly without knowing the “why” behind them.

Wrestling with and forming an understanding of the principles behind Agile/Lean requires perseverance. There are no shortcuts. Trial and error is expected, but not without wrestling with the reason why we’re trying to implement a practice in the first place. Racing from one good idea to the next requires little discipline. Little is learned when a practice is implemented without a grasp of the underlying principles. The failed practice is tossed out and a new one takes its place, awaiting a similar fate. The only way out of this rat race is learning why a particular framework, practice, methodology is the way it is and then identifying and carefully evaluating the problems we’re trying to solve and how the two align (or don’t.) There are no shortcuts. No silver bullets. No buzzwords to save the day.

Quote from EC: “You know, Mario Brothers is like crack and cocaine for kids”

Super Mario Bros.My twelve year old son was playing Super Mario Brothers on the Wii with his friend tonight. My son has played the game so much over the years he’s come to almost hate it. His friend isn’t there yet. While blazing through each screen with ease, EC casually blurts out that quote. His friend looks at him puzzled. Welcome to the club.