Better Programmer – a 12 Month Project
I wanted to become a better programmer. I have mentioned this in other posts and figured I should take some of my own advice. In reality this is more of a “I feel like I need to do some catching up as a programmer” instinct than anything. Technology is changing so fast and there is so much of it around it is easy to get lost in all of it. I have been working in the industry for just about 5 years, but lately feel like I don’t have a great grasp of a lot of the simple concepts. I want to Google less and just code more. Being able to work how to do some simple code without stopping to find an example. There are things that seem trivial that I have done before and feel like I should know how to do, but end up needing to find an example on-line to finish the code.
Part of this was brought up by a comment a co-worker made to me. He said, “It seems like students know how to copy code, but don’t know how to write it”. After looking at how I code, I had to agree and I wanted to be a better programmer. I tend to Google a question and end up on StackOverflow or some other blog usually to end up copying the code and them making some small modifications to make it would for my needs. I started looking at more of my students and found the ones that understood the code and didn’t really copy it out of the book or on-line were doing much better than the ones that did.
I figured I would try a new way of learning things. the idea is to take 12 months to be a better programmer. I would focus on one technology/language for a month. Study every part of it that I can get my hands on. At the same time practice as many parts as I could. Practicing, I hope, would be the key. I would need to focus on the chosen language or tech for one complete month. Without all the distractions of other tech to grab my attention, I would be free to explore each part of the technology. I have seen other blogs and developers work through a project a day or week in a specific area and taking the idea up a level to a broader sense seems like a good thing. As I document the process and my progress I hope to also document areas of the tech that I could focus on later. Then come back to that tech and focus on it even more after my year is compete.
In the end I decided to do a couple solutions. As I write this it is November and I wanted to get started sooner rather than later. I decided I would start now and go though December of the following year. First, the holidays can really mess with this schedule and second why wait till the first of the year to get started. There is some research that would need to be done to find resources for each of the tech anyway so the extra time would help with some of that. Second, I would combine the things that made sense to combine and leave others the I want to spend more time on for a full month. Last I would eliminate some things off the list. I wanted to work on fundamentals and specific new tech like Angular might have to wait. Unfortunately that is the sacrifice to keeping things moving and on schedule.
I also decided to give myself some leeway with the tech I was focusing on. If I felt pretty confident with the tech I could move on to something else earlier and before the month is over. I would need some sort of test in order to pass this point and I will be looking at a couple, either a certification or a simple test on-line to test my understanding. So the final process to the month would be to test my knowledge with some testing or certification site.
The hope is to achieve a few goals. First and for most to to less reliant on Google to write code. Second, gain more understanding of the technology I love to work with. Finally, the side benefit is to blog more consistently, share the knowledge that I am gaining and solidify that knowledge in my mind. Becoming a better programmer is going to be an ongoing process, but I feel like taking this time to focus on one piece of it at a time would make it easier to get to my goal.