Two Weeks Left in "Principles of Computing"

I managed last week with data structures and inheritance swimmingly. These two are right up my ontologist's alley. This week's recursion topic is a mind-bender, but I am wading through it. I still struggle with the more math-heavy aspects of the class, though.

There are two parts to the class besides the material: homework and mini-projects. The homework is more a quiz-style format. There are approx. 10-12 multiple choice questions. I have found that these questions are extremely hard for me to grok, and almost always math-heavy. The mini-projects are the actual coding tasks. They include things like simulations of zombie apocalypse, recreating the 2048 game, and word wrangler.

Usually, I need the week to watch the videos and work through the math/coding notes and do the practice activities. I prefer to start the mini-project by Sat to have both days of the weekend to work on it. There isn't much time in there for the hours I would need to finish the homework, so I usually drop it, or make one attempt and then leave my crappy score. There is a very real disparity between how well I can do on the homework and how I do on the mini-projects. I pull a 100% on the mini-projects every time.

It is really unclear to me how much emphasis I should be placing on the fact that I am throwing homework under the bus. I am not too worried about the number grade I get for the class; I am more interested in gaining the knowledge. That said, it still isn't clear to me how much I am leaving at the table by not dropping the class now and switching to a discrete math class, and later returning when I have a better handle.

Even though there is a follow-on class in Algorithms, I am thinking that I will wrap up this Principles of Computing class, then switch to a discrete maths class. Once I have that, I will pick up an Algorithms class. Luckily, Coursera has two: an algorithmic thinking class that is part of this series, and another two-part course done in Java. If I can catch the two-part one in Java, that might be a better choice: more in depth and exposure to Java.

Halfway Through Principles of Computing

So I am at the halfway point in the class, and seriously thinking of bailing. These last weeks of probability, randomness, and combinatorics have really put the pressure on me. I don't think necessarily the class is the problem. Rather, the problem is the lack of a discrete math background and the lack of sufficient spare time to make up for it. I did intend to work through a Discrete Math course, but I was waiting until this series was done. In retrospect, I think it would have been better to do the Math first :).

So, these past two weeks have been kicking my learning-to-program butt. I was thinking I should pull out and isolate work on the maths. I can always return to the programming after I have a handle on the maths. I found a couple of books to start creating a lesson plan, and I checked out the syllabus for my programming class to make sure I cover all of the relevant topics. To my surprise, this looks like the last week focusing on maths!! Instead, next week we move onto data types and inheritance. Oh definitely more up my alley.

My current plan is to stick with the class one more week and see if there are still big gaping holes to fill. I can always back out next week. I'd really hate to lose momentum in this series. I finished this week's mini-project with a perfect score, and if I can at least pass the homework, I think it will be fine.

About Halfway Through Intro Programming

We are hitting week 5 in the Coursera class I am taking. We just finished the pong game. I was a little disappointed that I did not seem to fix one of the scoring issues I had noted. I really thought I had it fixed, but no. Pong was quite a jump in complexity from the previous mini-projects that are due weekly. I had to scramble a bit more than usual to finish the work.

Python is a fine little language, but I still prefer Ruby for some reason. The Python's usage of the whitespace annoys me. But over all, they are pretty similar scripting languages. Kind of six of one... as far as I am concerned.

I think most of the value for me has been in the UI bits of the class, especially the animation. It isn't something that really comes up when one is trying to, say, find the number of politicians in a data set without an end date to their terms in office, or the number of entities that are typed as people and organizations :) Just generate a list and Bob's your uncle. While I like the expansion of my tool set, it isn't overly interesting enough to me to make me want to do UI or client-side programming. Good to know!

Python is a blast!

I am probably in the beginner/intermediate range for programming. I have used Ruby tons, but I wanted to learn more about coding. (Totally self taught...)

I signed up for Coursera's Learn to Program: Crafting Quality Code, but it uses Python. I didn't fancy trying to learn Python *and* the prinicples for the class, so I am reviewing the basics with the already finished class Learn to Program: The Fundamentals.

Python has been lots of fun so far. I am two weeks into the Fundamentals. I have taken two quizzes and have started the first homework. I had some problems getting Python's IDLE to play nicely on my Mac, but I had to fix my Tcl/Tk installation. Pretty straight-forward fix! And, I am loving Python's ease of use so far.