That may sound like a very depressing title, but keep reading.
I’ve been listening to Code Newbie podcast, especially Episode 60, Impostor Syndrome (an interview with Alicia Liu). I, according to the episode, really don’t have Impostor Syndrome. Few people do. She’s pointed out that it has become a buzzword.Â Right now my feelings of “code inadequacy” are not from any syndrome, they are from learning new stuff. Of course I am not good at new stuff, I am still struggling to learn it!
That being said, I do wonder if “this is the right thing to pursue”. Alicia Liu does touch on this, that while coding is the new hotness, it really isn’t for everyone. The thing she said that resonated with me, is that coding as a job is (paraphrase mine)Â living in a state of failure. Nothing you code is going to work right the first time. I think it’s good to know this going in. I am kind of a perfectionist. I don’t like failing. I don’t like error messages. When I was a full timeÂ technical editor/writer my goal was to comb every documentÂ so well that the QA department wouldn’t find anything to bleed red ink on. But, after years, I finally realized that when someone marks everything you did up and changes it, it reallyÂ isn’t personal. A second set of eyes is always going to see things to change, or point out how they would have done something differently.Â I’m still learning this, honestly, it’s hard to get it to sink in. But I’m hoping that this will help me for code reviews in the future. Knowing that your ugly code is being changed, not because you are a failure, but because that’s part of the process, and that you’ll get better with time. The code is still going to get thrown out, but itÂ isn’t a personal attack.
What do you think?
One thought on “Living in a State of Failure”