Initially, this blog was going to be about creating games and logging my experiences on the various tech that I encountered while creating my game. In reality, I only got a few steps beyond tinkering with the software. I say to myself, "Cool", then move on to the next shiney thing. I'll admit, I'm never going to be making games for a living and I'm okay with that.
Still, my trade is still software development, and it's one that I still enjoy. Every day, I get to solve a problem. My issue is that after I solve the problem, I never logged it anywhere. After a while, I would run into the same problem again which was just long enough to not remember how I fixed it the first time. My hope is that this blog will solve that.
Also, I hope that this journal will keep me honest in ensuring that I have a deeper knowledge of the tech that I do work with. When I'm complacent, I'll figure things out just enough to get the job done. The problem is I don't know if my implementation is the best solution because I never bothered to explore other possibilities. This can repeat itself when I encounter the same problem again.
This journal will have three types of entries.
- TechQuestion: This is an answer to a specific question that I ask myself when I'm in various parts of the Software Development Life Cycle.
- Cookbook: My plan is to have several entries that is a solution to a specific issue. This will be the majority of the entries in this blog.
- Reflection: Every once in a while, I reflect on myself and try to figure out how I can grow on a professional level. This entry will discuss my short comings and what I can do to fix that.
My hope is that this blog makes me a better software developer. It's okay if no one ever reads this, but if someone does and it helps them, then that's cool too.
