Sunday, March 20, 2016

March 20th update

This week, we focused even more on binary trees and how they work. A lot of it is stressing again how simple yet intricate these trees can be, a simple node possibly leading to a whole new tree of code. It's really fascinating how deceptively simple the concept is, and what benefits it has over a regular tree.

In a regular tree, while it may be simple to add more children to a single node without much hassle, an issue would be the problem of organization of the tree. A BST node can only have two children at a time, but a normal tree could blow up from having way too many. BST condenses this issue with only two off shoots that can possibly lead into more trees, and they do so in a way that makes it so adding/removing a node wouldn't kill the entire experience. The usage of nodes linking to each other reminds me a lot about linked lists, as if you remove one, you can patch the relationship to the next without too much of a problem.

Monday, March 14, 2016

March 14th late update

Apologies for the late update everybody! I'll make two posts this week to make up for the mistake, this one being the first one.

Well, we discussed binary trees in class this week and how they work. This is particularly interesting for me, an aspiring video game designer, as this illustrates the ability for some video games to have moral choices. Binary trees show the possibility of a single choice having multiple children, much like multiple branching paths in some games. I can only imagine how, when I properly learn the code for it, this would aid game design.

Thursday, March 3, 2016

The Advantage of Modern Programming's Object Oriented Programming (March 4th)

As I try my hand at some simple Javascript programming, it strikes me how rather advanced object oriented programming has progressed in terms of surpassing classical line by line forms of coding. While there is undeniable simplicity in the original forms of entering commands one by one, object oriented programming really has just made the entire experience far easier. It may be slightly more cumbersome to learn and excel in, but after having definite experience with the two, I would lean more towards object oriented due to its flexibility. The ability to go back and change code without breaking previous commands is far too useful to pass up, especially when you can branch off it very easily in comparison to line by line.