Game Dev Log #2: Progress
Computer language is relatively simple in terms of language but I’m discovering that there are some similar pitfalls. Just as with natural languages, you learn words before you learn grammar and only once you’ve truly mastered a language are you able to fluidly produce novel sentences completely of your own design and error free. That last part is the difficulty that mastery evades because the first part, creating novel sentences, is actually not too difficult for a novice. In many ways, you’re almost more likely to say absurdly original things. Of course they aren’t at all intelligible and serve to alienate your audience and yourself. Of course, it’s only through rigorous studying and many many mistakes that one overcomes that difficulty and starts to slowly integrate a language’s grammar into the way in which one both uses and understands the words one has at her disposal.
In the last couple days, I’ve tickled myself with coming up with these neat ways of solving the problems presented to me and then, in my attempts at realizing my solutions, have realized I’m just not using my words right. I create this or that and then discover that that’s not how Unity works (not that I then understand how it does work, just that it becomes clear to me that what I did does not work). Its been a source of some frustration, as one comment I made just earlier today to my partner sums up: “the best thing about having a hobby, is how ANGRY it makes you.”
But I’ve come a little ways since being angry and frustrated a number of times over the last few days. I have taken one of my solutions and refigured it so that it actually works as a code in Unity. I have a small array of strings, a random way of accessing them and they’re tied to a game object which displays the strings just as I want them. That, is some progress!