Week #9 SLOG

In week #8 I handed in my project. pep gave me innumerable things to fix but then again it always does. My minimax was logical and efficient but glitchy due in part to my temperamental computer. I don't think macbook airs were meant to program.

I have little to say as link lists are pretty easy. My biggest issue is with str representations. I'm still not exactly comfortable with formatting. However, on the lab the functions were pretty simple to complete. I think its because there is no branching with linked listed and the linear-ness (not a word, I apologize) is easy to work with. 

SLOG Week #8

My impressions on week 7 can be divided into two parts: those that are Assignment 2-related and those that are tree-related.

Tree-Related Impressions

When Diana introduced the tree ADT, I was pretty enthusiastic (or at least pretty enthusiastic as one can get about ADTs) because, being very new to programming, I had heard them being mentioned but never really knew what they were. I was then further enthused because many a time, while programming, I was running into difficulties where I needed to express a hierarchal relationship and trees presented a big game changer. 

In Week #7 we were introduced to binary trees which I found were a lot easier to work with than trees with an unlimited branching factor because, instead of needing both a for loop and recursion to visit all of the children one need only use a recursive formula that calls self.left and self.right. 

I did, however, need a little time to practice the different kinds of traversal: in-order, pre-order, and post-order. When doing lab 6's implement parenthesize, for some reason my instinct was to follow a path all the way to the bottom like this:

Assignment 2-Related Impressions

Assignment 2 is going well. My computer is being really glitchy but beyond that it's going well. I keep worrying that my TippyGameState apply_move method isn't efficient enough simply because, when it checks to see if the game is over, for ever every move it sees if in relation to that spot the surrounding spots are filled in order to create a tippy. It's about 4, 80 character lines of code which just seems really long to me but when I asked some of my friends they had similar lengths for theirs

Week #7

My impressions of Week 6:
I initially understand trees and their structure as an ADT, but I didn't understand how the coding worked. Particularly how this:

represented this:

However, I figured it out. If I'm not mistaken the structure is :

tree_variable = Tree(root value), descendants list, number of nodes per root. 

Week #5 : Recursion Tracing

I found recursion tracing to be extremely fun but requiring pretty intense focus. The lab was decently straightforward and I found I was able to trace them correctly once I got the hang of things. My only issue is designing recursive functions. I've tried doing a couple on my own and I find I'm a little slow.  Luckily I found a link with some practice questions here here which are useful.

Week #3 : Why geeks should write

Why geeks should write: 

I would argue that everyone should be able to write well. Writing in an effective and clear manner is invaluable in the workforce. In most jobs you'll need to make presentations or write reports. If one's report or presentation is well constructed, clear and as engaging as possible it will save both you and the reader time. If it is poorly constructed it will take the reader longer to find the information they need. If it is not clear they will spend unnecessary time trying to figure out what you meant, and potentially need to come to you for clarifications which wastes both of your time. Finally if it is not engaging the reader will be less likely to read it thoroughly and try to get through it as quickly as possible which could cause them to not absorb the information you're trying to present. 

While everyone should have good writing skills it is especially important for us geeks. Take doc strings. If yours is poorly written then the client will have trouble understanding what your methods and functions actually do. Secondly, I find good writing skills and good oral communication skills go pretty much hand in hand and a good geek needs be able to explain their theories and work effectively in both ways in order to be successful. Its no good being brilliant if no one understands what you did and can't use whatever you built. 

Slog Week #2

I'm writing this having just had my first lab. The assignment was pretty straightforward in easy except for one speed bump I had. I didn't realize initially that for __init__ you didn't have to type arguments in order to store data. What I mean is that I did not know you could do this :

So I was doing this:

It was initially pretty frustrating until I figured it out because it bothered me that whomever was using my class would not be able to add on to lists, for example, right away. They would have to create them first and then add on which I thought would just be tedious. Needless to say, when I figured that out I was both excited and felt like an idiot. 

Other than that little hiccup the lab went well. I think I got the quiz question right, however I think I could improve on my docstrings. My description was a little long and clunky. 

SLOG Week #1

SLOG Week #1

So it begins, the first SLOG post of many. Firstly, hello to whomever is reading this, I hope you enjoy this post and I'll try not to ramble (my main issue when it comes to writing). 

So far my impressions of this class are really good (and I'm not just saying that because I know the teaching staff is reading). The professor seems really nice and I thought it was nice how she made us introduce ourselves to our seat neighbours as before that I didn't know anyone in the class. I'm not saying this just to suck up but in my first year I honestly haven't met a computer science professor that wasn't likeable.

I've started on chapter one of the course readings. The language in the notes is pretty easy to comprehend and I found that my usual method of tackling readings (reading and then writing down notes, and then going over those notes highlighting the important parts), is working and I'm absorbing the information pretty well.

At section 1.1 I got super distracted because I'd never used the turtle class before and it's ridiculously fun to play with. I spent about an hour messing around with it before getting back to the course readings. 

Section 1.2 introduced abstract data types (ADTs) which were a little hard to wrap my head around initially but after reading the description carefully a couple times and trying to explain it in my own words I got it. The example of stacks really helped me a lot. I found it was a lot easier to explain ADTs to myself in the context of stacks.

In class I didn't have much difficulty understanding the lectures. The concepts are pretty easy for me right now, which makes sense as it is the beginning of the year so that's usually when the concepts are the easiest.
My biggest issue right now is probably that I don't remember all the vocabulary from last semester. It was easy to get by without learning it so I only really have a rough grasp of the technical terms. For example, parsing. I completely knew what it was and how to use it but I just did not know the proper name for it. Same thing with the word "delimiter". To solve this problem I've started to look up and write down the definitions of words I don't recognize that are used in the readings and in class and I'm learning them reasonably quickly.