Do I Code or Read?

I was contemplating this for a while. I guess the problem with why I don’t have motivation for programming is that I lack confidence that I’ll go down the so called correct path with writing code that would be reusable with multiple iterations of a project. I tend to have a higher personal standard than programming at work, since there isn’t a predefined standard for quality of code. It does tend to free up a lot of time pondering the right way to do something when the expectation is to just do it and doesn’t matter what the quality of the product. I don’t know, I’ve gotten better at writing modular reusable code at work, but some tasks require highly specialized code that once written can not be applied to other code bases without rewriting or heavy refactoring.

I have a high sense of pride with personal projects, because I want to scream to the world, “Hey, check this code out! I did this…” and I don’t want the first thing someone commenting on the code to say, “This sucks major balls!” That and my ego isn’t completely solid as to not fall over with major criticism. Well, I still have this problem with code and apt to defend any code I write with a passion. I realize this is the wrong way to approach opposition to my code, but well, I’m often not confident that the code is the correct way. It is both impressive and depressing to see someone write really beautiful code, but not understand the difference between the shit I wrote and crowning jewel the other person wrote.

I have a choice, I could either spend the next year or two writing shitty code until at some point I realize why my code sucks or someone comes along and shows me the error of my ways or I could just read a whole bunch of books from those that were in the trenches bleeding, sweating, failing and winning long before I even decided to enter this profession.

I guess I should have chosen the latter option sooner, but failing is a great learning experience. I enjoy doing it every day.

As much as I want to jump into coding, I think learning to be a journeyman coder and finally break out of the chains of a novice would provide a better experience than continuing with the false sense that I’m a master. I suppose I regret not realizing sooner, but at some point I lost perspective of where I was at and stopped growing. I knew people who fell into that pit and I vowed I would never follow in their footsteps. Realizing this, I think reading more and rereading several books in order to apply the knowledge will benefit me better.

Something tells me I should do both, but I usually go all out until I hit a brick wall.

Possibly Related Posts:


2 Comments.

  1. I have the same problem, and I agree it sure is more fun doing than just reading. Lately I’ve been trying to find podcasts and videos to listen to. Even though I do pay more attention when I’m actually reading, when I hear something interesting or confusing I can research it further if need be. But this way I can sort of do two things at once. :lol:

    Best of luck to you. I’m sure you’ll figure it out and become a better, more confident programmer soon. :)

    • Currently, I’ve had two months of reading and I’ve enjoyed it a lot. I’m learning a whole lot, I’m understanding a lot more and I’m learning about stuff that I was terrible at. I’m attempting to apply a lot of what I’ve learned so far to work and will in a couple of months applying more to personal projects. My confidence is improving, but well, I’ll be ready when I have a few Python books under my belt and more projects in that language finished.

      I know what you mean. I listen to books as well and while I learn a lot, I do have trouble paying attention as well. I catch enough to understand the basics of what is said, but usually what I’ll do is relisten two or three more times. It tends to allow me to pick up the parts that I missed while I was focusing on other tasks. Thanks!