So I am writing what I believe to be my frist post from the Comfy Lounge in the MC (my previous posts have been almost exclusively written from the SLC Great Hall or from my room in V1, with the exceptions of the 2 or 3 I wrote over my work term). As I sit here, the first thing I think of is how much I need a new pair of earphones considering my left one crackles and breaks up and the case that came with them broke a couple weeks ago when I dropped it on cement by accident. But that probably doesn’t interest any of you. I’ll get to the point, as there are several:
First off, my CS exam went just as predicted. With the exception of the confusing question I mentioned in my last post, I lost 1 mark on the entire exam. I didn’t in fact, miss any pages (thank God!), although a lot of course material was mysteriously absent from the test. On the other hand, it seems there is a great divide in CS 241 between pre-midterm and post-midterm. Before the midterm the course was pretty easy and the homework was quick, but the last assignment (*technically* next assignment considering it’s due tomorrow although I finished it on Monday) took me about 2 or 3 hours (about 6 or 7 including time it took to debug my first program and figuring out how best to do the 3rd one). It’s still nothing time-wise compared to CS134, though, where every programming assignment took me a good 5 hours easy (due to sheer volume of code required and not much else). This week’s assignment had to do with scanning. Unfortunately I can’t think of a way to get into detail about exactly what that means without taking up a lot of space and annoying the tl;dr people (for those who don’t get the reference, “tl;dr” is short for “too long; didn’t read”). Next week’s assignment is on parsing (which is hard to explain unless I explain scanning first), and then 2 assignments on code generation (where you basically, with the help of a scanner and parser, read in a program in one language and output it in binary so it can run on a computer). By the end of Assignment 10, I’ll have written a complete compiler for an incredibly rudimentary language (a very small subset of Java called “WL”). I have no idea what Assignment 11 will be then, but we’ll see.
Continuing in chronological order, I’ve dropped Math 146. I wasn’t doing particularly poorly in it (my estimated grade overall in the course to date is about 75%), but the assignments were taking a very long time to do and were just doing generally nasty things to my schedule (particularly the part of my schedule where I’d prefer to be sleeping). As such, I’ve dropped (unfortunately) to Math 136, which will have less homework (time-wise) but will also be much less fun (given the absence of Professor Marcoux, who is awesome) and be absent of the people I’ve become friends with in the Advanced Math classes. Oh well…there’s always Facebook and MSN
From what I’ve seen from my friends taking Math 136, they’re doing now what we did in Math 146 in the first 2 or 3 weeks of class. Then again, they’ve also been doing for the past 2 months what we just started (Interjection: MAN, I HATE THESE BLOODY EARPHONES!!!…sorry). It seems like it’s going to be really easy though; on Assignment 1 or 2 in Math 146 we were asked to prove a theorem. In Math 136 on this week’s assignment, they were asked to give a counterexample to the inverse of the same theorem (yeah, a single example, no proof, no generality, nothing, just a single counterexample. Now you know why I liked the advanced sections…). Oh well…I’ll grin and bear it for a month, get my 90, and get out. Not like it can be too much worse than Math 138…
Speaking of Math 138, the first Maple Lab was returned. Basically a Maple Lab is an assignment using a computer program called Maple (which is free to use on the UW servers but can be purchased from the CHIP for $21) where they give you a bunch of commands and a set of questions and tell you to use the commands to answer the questions. They’re really easy, but really time-consuming. As it turned out, my printer somehow forgot to print the last page of the assignment, but Nataliya allowed me to redo that page for credit, which I did. She seems like a really nice person, but she really needs to learn to teach better…*sigh*…
Course material-wise, we (somehow) finished Epsilon-Delta in about a week (don’t ask me how you can cover E-D in only a week…we spent about 2 months on it in Math 147…) and are dealing with limits of sequences and series (which I believe we glossed over in Grade 12 at my high school and did using E-D in Math 147) right now. I honestly have no idea how we’ve managed to spend about a week on that, since the basic premise is “the limit of a sequence is equal to the limit of the function defining that sequence”. But oh well…
Breaking chronological order for a moment, as I don’t think I’ve mentioned it, the Circuits midterm marks were posted the other day (I didn’t actually get my exam back, but given my mark and the amount of questions I answered, I can pretty much guess where I went right and wrong, as my estimate for my maximum possible mark on the exam based on what I answered was about 3% off what I got). I passed by a fairly wide margin (compared to what I was expecting anyway). I’ve spoken to a couple people who have taken DHW in the past and they said ECE 222 (which I’m taking next term in lieu of CS251) is pretty easy, so I think I’ll stick with DHW (assuming I make it past Circuits). If the current trend continues, I’m expecting somewhere between a 65 and 70 overall in the course by the end, and I’m OK with that given the material and the marking spread on the midterm (after doing a quick analysis of the exam marks in MS Excel, I found I’m about 4 spaces short of dead middle of the class mark-wise, and considering a good chunk of the class is repeating the course, I’m satisfied with that).
I think the big problem with Circuits is that the assignments don’t at all prepare you for the exams. In the textbook and tutorials and such, they deal with very easy problems; you are given 4 or 5 elements, a voltage or current source, usually obviously in series or parallel, and there may or may not be a trick to it, but it’s very rudimentary. Then on the exam, Professor El-Saadany prepares a huge circuit with 15+ elements, 7-10 sources (both Voltage and Current, some dependent some independent), most of which are neither in series nor parallel, and then you’re expected to solve it. That’s probably the biggest problem with the course; the preparatory material doesn’t do its job. Oh well, we’ll see what comes of it at the end…
Jumping back to chronological order, but still on the topic of Circuits, something kinda weird happened yesterday. Every Wednesday I have a 3-hour session of class blocked off as a lab. 4 times during the term we have a real lab (the second was last week, in which I got a very good mark despite doing an assignment by myself that was intended for 2 people), and the other times we have what is called a CDT. Basically a CDT is a 3-hour open-book test where there are TAs who help with questions and such. A couple of the TAs are really good, but some of them are not so much. So anyway, there was a CDT yesterday. My group had finished 3 of the 10 questions and were about halfway through the 4th when there was a 30-second blackout in the WEEF lab (the main Engineering computer lab in E2), which shut off all the computers, meaning we had to start over, an hour into the session. Instead of making us do that, though, they decided instead to let us finish for the day. I’m not exactly sure how it’ll be graded (considering my group had gotten none wrong of the first 3 questions while a friend of mine had lost 10 marks of the 6 or 7 her group had answered, so it wouldn’t be fair to give a mark based on current progress). So I basically got a free 2-hour break yesterday afternoon. And for those wondering why the WEEF lab doesn’t have backup power, I wondered that myself before thinking “why do I care? I get free marks and a 2-hour break from class”
We got our midterms back in Japanese class last night. As predicted, I once again did well in it. I made sure it made up for the fact that I botched the first term test, and it did. I did make a couple silly mistakes (notably mixing up the words for “to walk” and “to open”, which are very similar…apparently you can walk windows…or something…I dunno…), which I attribute to screwing up 2 midterms in the 2 days prior. Next week is our reading test where we have to recite a passage from the textbook and we get graded on how well we speak. In 101, we had to memorize the passage, which is why I completely screwed it up, but this term Misato-sensei says we can read from the textbook and memorizing will be worth bonus marks. Learning my lesson from 101, I’m going to give up the bonus marks, since I think I can do a really good job of it if I read it over a couple times and understand what I’m saying and use the textbook as a guide to where I am at any point.
In other Japan 102 news, we’ve been given our final term project. It’s the exact same as 101: Write a short skit (10-15 minutes) on any topic you want as long as you try to use as much vocabulary from 102 as possible and use very little from outside the course. Unfortunately, one of my group members doesn’t see it the same way I do, so we’ve decided to try to take a Japanese fairy tale and modernize it so it can be more “meaningful”. I dunno…we’ll see how it turns out since 4 of my group members (out of 5) are in favour of the idea. I just hope we can do a good job of it, especially considering the story was originally written in native Japanese, which we are nowhere near. I equate it to trying to tell the story of Snow White to someone with rudimentary conversational English knowledge (and thus having no idea what the words “dwarf”, “witch”, “magic”, etc. even mean). But they didn’t like my alternative idea, so we’ll see how it works out. I just hope we don’t waste too much time on his idea if it turns out he’s wrong…
And that’s pretty much a quick rundown of the past week as it’s been here. As always, feel free to contact me at uwmathblogger@gmail.com if you have any questions or comments. Until next time,
Lyle Waldman