Week 1

I’m a student at Makersquare in Austin, Texas.

That’s all the background you really need, but let’s dive a bit deeper. I have a life long love of computers, I mean using them and playing on them from when I could walk, life long. I was trying to make them talk to each other, because I knew they should be able to, before I had any concept of what made PC different from a Mac.

I’ve loved games my whole life, and I’ve always wanted to make them. Any game, any where, with anything. A deck of cards or a terminal window was all the same to me. This is what got me started.

I’ve been writing code for about 10 years, since I was 8. I’ve made some cash from it, but nothing really worth-while. Originally, I learned to code to make games, then I made one and I was good. But what really took me in was solving problems. Games are great, but they’re not as useful as a mortgage calculator or a application that displays words from a pre-processed list to help a class of school children learn their vocabulary words.

It’s a been a long journey, and I’ve taken my first steps toward making it my day-job. In the short time I’ve been here, I’ve grown a lot more than I would’ve thought. I knew the concepts, sure, but I never fully understood the e consequences of certain choices, or the implications of certain algorithms. I’d never had to worry about efficiency, so I never really tried to get a rock solid understanding of what Bi-O notation really represented, or what implications data structures had for the speed of my code. And when your primary interest is in games, all those performance problems come front and center. That’s the main take away after all of the gotchas in JavaScript that they went over. A solid language foundation layered over a compressed intro to computer science. The perfect summary of my first week.