Personal Narrative: My First Time In Programming

I will never forget the first time I started programming. I started with the hopes of creating a “Triple A” game title or a physics engine for a game. Oh how naïve I was, I thought I would be able to program anything. With the sights of programming in my eyes one night I found myself alone in my room. The room was dark, the screen was bright and filled with white and a blinking cursor. I stared at it as it daunted me until the void in my mind finally expanded with the question “What do I do now?” I thought I could start programming an entire physics engine by myself without any knowledge of the mathematics of physics, how physics engines work, the amount of time, work, and skilled mathematical wizards from MIT and the like would take to create one. Nor did I even know the basics of programming. This was the first brick wall that I had to get passed.
It was time for a plan. I …show more content…
They were always simple games, where they just told us what we needed to do and the parameters of how it should look and then simply told us just to do it. That may be intimating to some people, but certainly not to me. I liked the fact that I was able to solve problems on my own in order to have a final program that functioned how it was supposed to and not have someone constantly down my neck feeding me useless jargon and ultimately leaving me with less time for problem solving. In my opinion, this was such a good learning technique because it forced you out on the field all alone with nothing but a rock and stick in your hand and told to build a castle. This method was far superior then just taking tests and doing homework, like the tests that I took on the course. They were a bit difficult sometimes but ultimately useless. The so called “test” did not test my ability to actually program and understand logic nor did it represent any understanding of the given