Summer courses always go by too fast. The amount of work and material is compressed so tightly that it's a little hard to keep up with it as well as a job and the semblance of a social life. This week we had our first test in the course and while it wasn't quite what I expected, overall it wasn't too bad.
The test focused on mostly lecture topics with one problem that related to our first project. However, I was expecting at least one question on the assigned reading. See, for the day of the test we had at that point been assigned part of the introduction of our text, two sections on limits and an entire chapter (100 or so pages) on streams. Being the diligent student I am, I read all of that for the test, the last two parts the night before. Unfortunately the test didn't have a single question regarding the reading, or at least nothing that wasn't covered in the lecture. To be honest I was a little relieved, because my reading comprehension is not so great between 10 and 12 on the night before a test. It's just frustrating that I spent a significant time reading something I didn't need to, when I could have spent that time preparing differently for the test. Though in the end, this is a small gripe because I feel I did rather well on the test, so I probably shouldn't complain too much.
This does bring up an interesting debate I've noticed recently in college. The decision between using a text and not seems to be becoming a bigger issue with teachers, administration and students. Probably because the price of these books keep skyrocketing and are contributing to the increase in student debt and back problems. I've had teachers that didn't require a text and taught the whole course from their own notes and materials. And I can see how this could be very difficult for every professor to accomplish due to the time it would require to prepare all the material. Though I will say I feel like I have gotten more out of any lecture than out of any text I've every had to read. Not to say that I can't see the appeal of a text book. A centralized collection of information on a course is nice to have when you can't contact the teacher or a fellow student and you have a pressing question. I don't see this issue disappearing though, there's big money in text books and it's simply easier to teach out of one than not, but maybe someday the lug of weight I have/had to carry around will be a thing of the past.
Saturday, June 25, 2011
Sunday, June 19, 2011
It Takes Two For Summer Learning
Another week and another project. This time the problem of choice is the Stable Marriage algorithm. For those interested in it, please go here.
Perhaps more interesting is this was the first time I did pair programming for a project. Unlike the group project hell of grade/high school, pair programming has multiple benefits. After reading a couple of papers on it, one of which had dubious conclusions, I was slightly sold on the idea. With the addition of extra credit and an able partner with a similar schedule I decided to take the plunge. Here are my personal results.
Overall, I'd say the experience was pleasant. It took us about 7 hours of working, but we did the whole assignment in one run. Another person helped to do all the extraneous 'paperwork', i.e. setting up wikis, repositories, etc., in a shorter amount of time. Also having a second person to bounce ideas against helped wrap my head around implementing a working algorithm from the basic structure in my head. And probably most beneficial was another set of eyes to catch any errors in writing or syntax, and honestly this probably saved us the most amount of time. At one point or another we both mentioned that the other saved us several hours of beating our heads against a wall by finding an all to obvious but elusive bug.
However, the whole process wasn't painless. Given adequate time two different minds can come up with two wildly different solutions to a problem. Trying to combine those solutions into one program can be quite tricky. I fear our final solution was more complicated than it needed to be due to the cobbled style of our writing. We attempted to allow each other to write what we had in our heads, and did our best to make the two ideas work together. On the whole it was very successful and we found a working and optimal solution that met the project guidelines. Though I do think though that this led to more time spent coding and debugging than if we had each wholly implemented our own solution.
Saying all of this I still believe that pair programming to be a positive exercise in coding and I intend to attempt to do the rest of the projects in a pair. If only because those extra points make it such an easy choice.
Perhaps more interesting is this was the first time I did pair programming for a project. Unlike the group project hell of grade/high school, pair programming has multiple benefits. After reading a couple of papers on it, one of which had dubious conclusions, I was slightly sold on the idea. With the addition of extra credit and an able partner with a similar schedule I decided to take the plunge. Here are my personal results.
Overall, I'd say the experience was pleasant. It took us about 7 hours of working, but we did the whole assignment in one run. Another person helped to do all the extraneous 'paperwork', i.e. setting up wikis, repositories, etc., in a shorter amount of time. Also having a second person to bounce ideas against helped wrap my head around implementing a working algorithm from the basic structure in my head. And probably most beneficial was another set of eyes to catch any errors in writing or syntax, and honestly this probably saved us the most amount of time. At one point or another we both mentioned that the other saved us several hours of beating our heads against a wall by finding an all to obvious but elusive bug.
However, the whole process wasn't painless. Given adequate time two different minds can come up with two wildly different solutions to a problem. Trying to combine those solutions into one program can be quite tricky. I fear our final solution was more complicated than it needed to be due to the cobbled style of our writing. We attempted to allow each other to write what we had in our heads, and did our best to make the two ideas work together. On the whole it was very successful and we found a working and optimal solution that met the project guidelines. Though I do think though that this led to more time spent coding and debugging than if we had each wholly implemented our own solution.
Saying all of this I still believe that pair programming to be a positive exercise in coding and I intend to attempt to do the rest of the projects in a pair. If only because those extra points make it such an easy choice.
Monday, June 13, 2011
A New Semester, New Self Taught Unix
In an effort to score some extra credit for my summer class at UT, I return to this blog. The topics will probably be much more Computer Science-y than previous posts, so you are warned if you're not a visitor from my class.
I am taking CS378, which is a course on the Standard Template Library (STL) and Generic Programming in C++. The class is taught by Professor Downing, who I've not had the pleasure of having yet at UT, and so far it's a pretty interesting course. Fortuitously I took a course on C++ last semester, so a lot the intro of the course is familiar ground. (Though I am now dreading returning to Java since it's been almost a year since I had to use it...).
For this week's post I'm going to talk about the first assignment for the class, which I finished up on Sunday. The task was to write a program to solve a variation of the Collatz problem. That part of the assignment was a breeze, even the added component of inserting some variation of a cache to speed up the computation. The more difficult part of the assignment was learning (teaching myself) how to use the infrastructure required for the course. In particular, this class requires a project host (with issue tracker and wiki) and a source control repository. And as I am learning is a recurring theme in CS courses at UT, I had to develop a slightly deeper skill set of Unix commands.
Having completed the Biochemistry program at UT it's very interesting comparing the styles of teaching in that program to the ones in the CS department. Biochem tended to be very hand holding on the practical aspects and intensely rigorous on the theory, while CS appears to do the opposite. I don't mean to say that theory courses or tests in CS are easy, but in my experience they're easier than my previous studies. However the amount of skill I've been required to develop either on my own or with fellow students is staggering in CS as compared to Biochem. The funny thing is I think I might like the CS style more, but then again I'm a bit of a masochist.
I am taking CS378, which is a course on the Standard Template Library (STL) and Generic Programming in C++. The class is taught by Professor Downing, who I've not had the pleasure of having yet at UT, and so far it's a pretty interesting course. Fortuitously I took a course on C++ last semester, so a lot the intro of the course is familiar ground. (Though I am now dreading returning to Java since it's been almost a year since I had to use it...).
For this week's post I'm going to talk about the first assignment for the class, which I finished up on Sunday. The task was to write a program to solve a variation of the Collatz problem. That part of the assignment was a breeze, even the added component of inserting some variation of a cache to speed up the computation. The more difficult part of the assignment was learning (teaching myself) how to use the infrastructure required for the course. In particular, this class requires a project host (with issue tracker and wiki) and a source control repository. And as I am learning is a recurring theme in CS courses at UT, I had to develop a slightly deeper skill set of Unix commands.
Having completed the Biochemistry program at UT it's very interesting comparing the styles of teaching in that program to the ones in the CS department. Biochem tended to be very hand holding on the practical aspects and intensely rigorous on the theory, while CS appears to do the opposite. I don't mean to say that theory courses or tests in CS are easy, but in my experience they're easier than my previous studies. However the amount of skill I've been required to develop either on my own or with fellow students is staggering in CS as compared to Biochem. The funny thing is I think I might like the CS style more, but then again I'm a bit of a masochist.
Sunday, January 16, 2011
New Year, New Promises
So... how is everyone? I'm doing great myself, just thought I'd stop by and maybe write a few things. Only if it's cool with you. Is it? It is? Good, well let's begin then.
After a quick perusal of my last post it appears I was writing about Mass Effect 2. Well you'll be glad to know I beat the shit out of it not long after I posted. I finally chose Tali in the end, and got a huge punch in the balls when I STILL didn't get to see her face. Though it was still pretty cool I guess... Anyway I lost one character in the suicide mission, I forget his name it was the scaly guy. At some point I plan on beating it with everyone alive, but I'm going to keep my first save and play Mass Effect 3 with it cause I like consequences.
Now what has happened in the almost year since I posted? A lot. Not an alot mind you, just quite a bit. Most of it is inconsequnetial to a gaming blog, but I did beat a few games and have started to focus on beating more. I'll try to do some write-ups over the next few posts on the specifics.
Also I might be taking this blog in a slightly different direction. I plan to continue the gaming updates, but I've found my lack of income has forced me to eat at home more and that has led to me cooking more. I'm not great, I'm not even that good, but I plan on trying new things. And if any of those things end up being interesting, I'll be sure to fill you all in. With pictures too! Excited aren't ya?
Anyway, I should be able to go home soon, so I'll see ya round.
After a quick perusal of my last post it appears I was writing about Mass Effect 2. Well you'll be glad to know I beat the shit out of it not long after I posted. I finally chose Tali in the end, and got a huge punch in the balls when I STILL didn't get to see her face. Though it was still pretty cool I guess... Anyway I lost one character in the suicide mission, I forget his name it was the scaly guy. At some point I plan on beating it with everyone alive, but I'm going to keep my first save and play Mass Effect 3 with it cause I like consequences.
Now what has happened in the almost year since I posted? A lot. Not an alot mind you, just quite a bit. Most of it is inconsequnetial to a gaming blog, but I did beat a few games and have started to focus on beating more. I'll try to do some write-ups over the next few posts on the specifics.
Also I might be taking this blog in a slightly different direction. I plan to continue the gaming updates, but I've found my lack of income has forced me to eat at home more and that has led to me cooking more. I'm not great, I'm not even that good, but I plan on trying new things. And if any of those things end up being interesting, I'll be sure to fill you all in. With pictures too! Excited aren't ya?
Anyway, I should be able to go home soon, so I'll see ya round.
Monday, March 15, 2010
No Excuse
Frankly I'm lazy and I got distracted and I'm sorry. Can't say it won't happen again, because it will. I will say I'll try to keep it to a minimum.
The past three weeks have been rather interesting gaming wise. I finally beat Mass Effect and immediately jumped into the sequel. I sat down for some controller passing Bioshock 2 multiplayer, and I jumped into the changes in Portal.
Mass Effect, I will leave to next week. I'm going to try my hand at an actual review, not this stream of consciousness bullshit. On the whole I really liked the game, but it did have a few flaws. Stay tuned!
I haven't started Bioshock 2 proper, but I sat down with some friends and we fired up the online multiplayer and passed around the controller after each game. There's nothing too new or great about this game's multiplayer, but it sure is fun and more so with friends. It did make me want to play the single player much more and I look forward to jumping into it.
This past week Valve introduced some new things into Portal in anticipation of the announcement of Portal 2. A radio is hidden in each level and it must be taken to specific place to retrieve a certain signal. It adds another puzzle to each level and it actually very fun. I've only done about 10-12 of them, but I have to say it was a great idea on Valve's part.
Mass Effect 2 is in a word fucking-amazing. They clearly took the majority of the complaints from the first one and did something about it, generally for the better. Gone are the over used set pieces and annoying as balls mako portions. Each area has an unique look and feel, and even the side missions have more in depth and interesting story elements. The resource mining is interesting at first, but then boring as hell. At least it looks like you can stop well short of draining all the planets and be set for the whole game. As a game, the best way I can describe ME2 is to compare it to a sci-fi tv show. Each mission, story or secondary, has its own story and area and they feel unique and different while sticking to the main idea of the game very similar to the episodic format of many sci-fi shows (the onboard relationship stuff reminds me of filler/characterization episodes). The combat is really fun, but pretty different. I like it, but I could understand disagreement if a person wasn't keen on third person cover shooter mechanics.
My recent play time with ME2 has brought about a rather humorous story. Before I had played any of it, I had heard that the relationship storyline with Jack was pretty deep and very interesting. So far I've been 'pursuing' Jack, but I've just discovered that Shepard can have a relationship with Tali (my favorite character from ME1) and I've reached a dilemma. Neither character will allow two-timing and I find each fascinating and I'm at a loss at who to pick.
Now right about now I'm sure you're saying, "Hey, just save at the decision point and do both." Well, concerned listener, that's a good idea if I hadn't decided to play the game straight, at least my first time through. In the first one I never went back to change a decision and lived with all the consequences, and I plan to do so for ME2 as well. The story is infinitely more interesting when the choices I make for Shepard have real consequences.
So I wallow in agony over which fictional woman I want to bang. The homicidal super powered merc or the super cute mechanic alien. Decision, decisions...
The past three weeks have been rather interesting gaming wise. I finally beat Mass Effect and immediately jumped into the sequel. I sat down for some controller passing Bioshock 2 multiplayer, and I jumped into the changes in Portal.
Mass Effect, I will leave to next week. I'm going to try my hand at an actual review, not this stream of consciousness bullshit. On the whole I really liked the game, but it did have a few flaws. Stay tuned!
I haven't started Bioshock 2 proper, but I sat down with some friends and we fired up the online multiplayer and passed around the controller after each game. There's nothing too new or great about this game's multiplayer, but it sure is fun and more so with friends. It did make me want to play the single player much more and I look forward to jumping into it.
This past week Valve introduced some new things into Portal in anticipation of the announcement of Portal 2. A radio is hidden in each level and it must be taken to specific place to retrieve a certain signal. It adds another puzzle to each level and it actually very fun. I've only done about 10-12 of them, but I have to say it was a great idea on Valve's part.
Mass Effect 2 is in a word fucking-amazing. They clearly took the majority of the complaints from the first one and did something about it, generally for the better. Gone are the over used set pieces and annoying as balls mako portions. Each area has an unique look and feel, and even the side missions have more in depth and interesting story elements. The resource mining is interesting at first, but then boring as hell. At least it looks like you can stop well short of draining all the planets and be set for the whole game. As a game, the best way I can describe ME2 is to compare it to a sci-fi tv show. Each mission, story or secondary, has its own story and area and they feel unique and different while sticking to the main idea of the game very similar to the episodic format of many sci-fi shows (the onboard relationship stuff reminds me of filler/characterization episodes). The combat is really fun, but pretty different. I like it, but I could understand disagreement if a person wasn't keen on third person cover shooter mechanics.
My recent play time with ME2 has brought about a rather humorous story. Before I had played any of it, I had heard that the relationship storyline with Jack was pretty deep and very interesting. So far I've been 'pursuing' Jack, but I've just discovered that Shepard can have a relationship with Tali (my favorite character from ME1) and I've reached a dilemma. Neither character will allow two-timing and I find each fascinating and I'm at a loss at who to pick.
Now right about now I'm sure you're saying, "Hey, just save at the decision point and do both." Well, concerned listener, that's a good idea if I hadn't decided to play the game straight, at least my first time through. In the first one I never went back to change a decision and lived with all the consequences, and I plan to do so for ME2 as well. The story is infinitely more interesting when the choices I make for Shepard have real consequences.
So I wallow in agony over which fictional woman I want to bang. The homicidal super powered merc or the super cute mechanic alien. Decision, decisions...
Tuesday, February 23, 2010
Late!
I must apologize on the late update, I know how important this is to all of you. Fear not, for I am mere hours late and not days.
Anyway...
Another week, another clusterfuck of work and school. Who would have thought one class could produce as much work as 3? Well I did get in some more Mass Effect play time and I near the end. I plan to jump right into Mass Effect 2 right as I finish to keep the story going.
This week I'd like to talk about moral choices. Morality has become a more common theme in gaming recently. Though the first game I can think of that sported some sort of risk/reward system would be Ultima IV. While it may not have been THE first, it was the first for the Ultima series. Activities that had been encouraged in the past(stealing from homes, etc.) were frowned upon or punished. Sure it was simple, but it added such depth to gameplay, and yet it was an idea most developers ignored until recently.
Bioware started a good/evil trend in Knights of the Old Republic (KOTOR); the mechanic has made an appearance of some form in all their games since. I'm going to talk about Mass Effect since it's the game I've been playing lately.
In ME most of the choices available in the game fall in one of three categories: Paragon, Renegade and neutral. (I'm not quite sure why a neutral option is even available, there's no reward for following that choice style and most of the neutral conversation options put you in the worst position.)
Being a paragon or renegade gives you specialized dialog options based on that status's bonus skill(charm for paragon and intimidate for renegade.) Paragons tend to be the goody two shoes of the universe, they believe any wrong can be righted. While renegades do what they have to to get the job done. It's a slight twist on the typical good/evil, the paragon options are almost universally good, but not all the renegade options are evil. A good amount are rude and insensitive or close minded, but some remind me of hard decisions that have to be made for the greater good.
What do moral choices bring to gaming?
They provide more immersion in a good story. I realize 'immersion' is one of those gaming buzzword, but when I can change how a story develops (even when it's a small change or simply cosmetic) I grow more attached to my characters. Also choices can lead to more exciting stories. Most heroes I grew up with had to make hard choices; who to save, whether to kill the bad guy, etc. And these choices are a great deal of what make heroes heroic. Being able to make those same choices, whether they are right or wrong, gives me some sense of being that hero or villain. It's a feeling that can't be recreated in prose or video.
Maybe that's why I can't help but be the sickly sweet good guy in all these games...
Anyway...
Another week, another clusterfuck of work and school. Who would have thought one class could produce as much work as 3? Well I did get in some more Mass Effect play time and I near the end. I plan to jump right into Mass Effect 2 right as I finish to keep the story going.
This week I'd like to talk about moral choices. Morality has become a more common theme in gaming recently. Though the first game I can think of that sported some sort of risk/reward system would be Ultima IV. While it may not have been THE first, it was the first for the Ultima series. Activities that had been encouraged in the past(stealing from homes, etc.) were frowned upon or punished. Sure it was simple, but it added such depth to gameplay, and yet it was an idea most developers ignored until recently.
Bioware started a good/evil trend in Knights of the Old Republic (KOTOR); the mechanic has made an appearance of some form in all their games since. I'm going to talk about Mass Effect since it's the game I've been playing lately.
In ME most of the choices available in the game fall in one of three categories: Paragon, Renegade and neutral. (I'm not quite sure why a neutral option is even available, there's no reward for following that choice style and most of the neutral conversation options put you in the worst position.)
Being a paragon or renegade gives you specialized dialog options based on that status's bonus skill(charm for paragon and intimidate for renegade.) Paragons tend to be the goody two shoes of the universe, they believe any wrong can be righted. While renegades do what they have to to get the job done. It's a slight twist on the typical good/evil, the paragon options are almost universally good, but not all the renegade options are evil. A good amount are rude and insensitive or close minded, but some remind me of hard decisions that have to be made for the greater good.
What do moral choices bring to gaming?
They provide more immersion in a good story. I realize 'immersion' is one of those gaming buzzword, but when I can change how a story develops (even when it's a small change or simply cosmetic) I grow more attached to my characters. Also choices can lead to more exciting stories. Most heroes I grew up with had to make hard choices; who to save, whether to kill the bad guy, etc. And these choices are a great deal of what make heroes heroic. Being able to make those same choices, whether they are right or wrong, gives me some sense of being that hero or villain. It's a feeling that can't be recreated in prose or video.
Maybe that's why I can't help but be the sickly sweet good guy in all these games...
Monday, February 15, 2010
Vday Exhaustion
Hate to say it, but it's gonna be a short one this week. Due to an extremely busy work weekend and the excessive alcohol consumption required to forget said weekend I didn't get much time with Mass Effect this week.
Mass Effect:
Much the same as last week. I've been exploring all the side worlds and doing secondary quests. I do think this game really needs a proper autosave, exploring a planet for half an hour only to die at the last part of it and getting sent back to planet drop is a tad annoying.
I did progress the main story by going to Noveria and got to play with conversation trees again. Though dealing with cut throat business people tends to make me choose renegade choices. I'm enjoying the progressing story and I hope to get more into it during this week.
Well that's all I gotta say for now.
THREEPEAT!
Mass Effect:
Much the same as last week. I've been exploring all the side worlds and doing secondary quests. I do think this game really needs a proper autosave, exploring a planet for half an hour only to die at the last part of it and getting sent back to planet drop is a tad annoying.
I did progress the main story by going to Noveria and got to play with conversation trees again. Though dealing with cut throat business people tends to make me choose renegade choices. I'm enjoying the progressing story and I hope to get more into it during this week.
Well that's all I gotta say for now.
THREEPEAT!
Subscribe to:
Posts (Atom)