Final Blog Post

I thought that this semester was pretty good. I like python, so using it and learning about it for most of the semester was nice. I thought that the sudden jump to the app inventor at the very end was kind of abrupt, but we had to jump to it some way, so whatever. If I have one complaint about this semester, it would probably be that we almost spent too much time on python. After a certain period of time spent on just python, it all started to kind of blend together, and the individual lessons we were learning felt less distinct from each other. Python is a full programming language, so I understand the need to cover a lot of material, but learning about only python for nearly an entire semester certainly got tiring, if not uninteresting. Maybe we could have done a bit of processing either at the beginning or somewhere in the middle, just to switch things around and give a bit of variety, rather than putting the two new things both towards the very end and spending all of our time basically since we started Jeroo on the same programming language. There was variety in terms of what the different labs were about, and some of them (such as the one with the Caesar shift) taught me some interesting things that were only tangentially related to what we were learning at the time. So, in short, while I enjoyed the class and like programming in python a lot, I thought that maybe we could have mixed it up a bit towards the middle of the semester, so as to keep it all from running together. Also, though I think I’ve mentioned this in an earlier blog post, I wish we could have used Coding Bat more often. I liked the way that it helped to teach all the concepts we were learning, and the constant introduction of widely varied problems on the same subject helped to keep it fresh. They were like mini-labs, and I thought they were pretty fun. The extra involved with completed certain amounts of them was also something that I liked.

Make Quiz and Take Quiz

That was kind of frustrating, to be honest. I'm sitting there trying to figure out what's wrong for nearly forty minutes, and it turns out I could have figured out what's wrong in forty seconds. I suppose that's always true for programming, though. You have a sweeping, elaborate program, in which all is in its proper place... and one typo will send the entire thing crashing down, requiring you to pore over the entire code in order to identify the problem.

App Inventor

Its fine, I suppose. I think I would've preferred a final based on python, but this works too, I suppose. One of the main frustrations is that its a lot like scratch. It just seems like a really simple platform to base the final off of. Of course, making the final in python might have led to some lower grades over all as people run out of time on the final, but the App Inventor just seems a bit too far the other way.

Processing

Processing is lots of fun. I don't think I like it quite as much as Python in that python can do things other than make pretty pictures, but it was still fun to use. It was also pretty useful for figuring out some parts of java syntax. By looking through the tutorials and examples for this comparatively simple language I figured out some things that had been puzzling me about the layout of java, which was nice. Not to mention that some of the images and such that Processing could be used to make were very impressive. I in particular liked the fractals and geometric models.

Ivy Bridge

That new processor looks like it'll be really cool. Not only will it be a lot smaller than those that are around today, which will help to make things more compact, but it'll be a lot cheaper to charge. That will be nice, having something that draws off less power, costs less to power, and gives a larger interval in between charges. Maybe its just the fact that my laptop is beginning the final stage of its life and so has all of the charge retention of a wet rag that makes me fixate on this aspect above all of the others, but its still nice.