User Tools

Site Tools


blog:fall2015:dm016807:journal

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
blog:fall2015:dm016807:journal [2015/11/02 21:11] dm016807blog:fall2015:dm016807:journal [2015/12/07 22:12] (current) – [UNIX] dm016807
Line 68: Line 68:
 ====UNIX==== ====UNIX====
 This week in UNIX, we looked at an abundance of ways to treat our ASCII cat in ways PETA would not appreciate.  We learned different programs we could have running, how to kill them, how to freeze them, how to reanimate them (sometimes causing them to actually die, since they don't when frozen).  Though I think technically they were already dead and just weren't visually represented as such until you tried to unfreeze them.  We also worked on ways to grep things, like acquiring specific usernames and number of terminals open.  The project for the week is a bit reminiscent of the puzzle boxes of the past.  It's a data recovery exercise, which mostly involves our ability to utilize the manual and our knowledge to manipulate data.  I think it'll be another one of those projects if you don't get right away, you'll bang your head until you do get it, and then you might bang it one more time for not realizing how simple the answer was.  Class on Thursday was pretty much cancelled by NYSEG, so the entry's a bit shorter on relevant info for the week. This week in UNIX, we looked at an abundance of ways to treat our ASCII cat in ways PETA would not appreciate.  We learned different programs we could have running, how to kill them, how to freeze them, how to reanimate them (sometimes causing them to actually die, since they don't when frozen).  Though I think technically they were already dead and just weren't visually represented as such until you tried to unfreeze them.  We also worked on ways to grep things, like acquiring specific usernames and number of terminals open.  The project for the week is a bit reminiscent of the puzzle boxes of the past.  It's a data recovery exercise, which mostly involves our ability to utilize the manual and our knowledge to manipulate data.  I think it'll be another one of those projects if you don't get right away, you'll bang your head until you do get it, and then you might bang it one more time for not realizing how simple the answer was.  Class on Thursday was pretty much cancelled by NYSEG, so the entry's a bit shorter on relevant info for the week.
 +
 +====Week 9====
 +====C Prog====
 +We have continued on with C++ learnings, with tuesday's class mostly being a review of the workings of a variety of permissions between parents and children, namely being that children do not have access to their parents privates.  Past the review of rectangle.cc, with all of it's this ->, return, setting and getting of the public and private types, we now have digit.cc.  We left off after setting up how to increment our digit based on bit, decimal, value, etc. to have decrement left over for Joe.  However despite being in class past the scheduled time, we never really ended up writing much new code and more so just going into other ideas based around it.  As for the lab this week it's a bit more interesting in my opinion because we're dealing with very simple ciphers.  In this case, a caesar cipher to encode and decode with.  From hearing what we needed to do, it sounded extremely simple, though on closer investigation that is not so much the case.  It still feels easier than our last project though, so that's something.  I think since this has like a real world spy feel, despite it being extremely dumbed down and simplified, it makes it a bit more fun.
 +
 +====UNIX====
 +In UNIX we went over some more commands you can use in vi, and some in nano, to make life a little easier when coding.  Most of Thursday's class was more of a review for people who had finished last weeks project, because some people had still been struggling with how to do it, or understanding what they did to do what they did.  It definitely felt like the type of project that you could pretty easily throw your keyboard and go to a bar after trying to think on it alone in the dark for a couple hours.  Luckily there's power in numbers.  Even if some of those numbers lead you astray with a bunch of simple arithmetic to figure out values and places you don't need.  This weeks project is calculating the week of the semester based on user input for the name of the semester, start and ending dates, list of days class does not meet and day to check for the semester week.  There's a lot of information at hand, but it doesn't seem conceptually all that awful, maybe that's because of what we had to deal with last week.  By contrast this seems fairly simple, and it's just a little bit of a headache to figure out how to set it all up to recall and read properly, but once you get into the flow it should be easy to finish out.  
 +
 +====Week 10====
 +====C Prog====
 +Just one more week, and then there's a break.  You can do this.  And then there's two weeks, and the final experience and personal know how stuff.  You're screwed.  As for class this week, we worked more on digit.cc, learning more in the workings of c++ and how much more we have to write to it than c.  Matt did mention the possibility of the void digit :: decrement() being on our end of year experience thing, make a mental note of that.  Maybe even look into working on it ahead of time, you know, to make it that much easier.  The project continues to grow with all the various get and set base, sum, carry accessor functions, while decrementing and incrementing the stuff.  As for the projects, they continue to get more complex as expected.  Need to put more time into them , only 3 weeks of class left, slacking will quickly snowball downhill.  The last project was mostly confusing in figuring out how to use the !=EOF, getting information from cypher.key files and setting that up as a default if no cypher key was given from stdin, fun things of that nature.  I understood how the last project worked out, and could look at code to recognize what was happening, but writing it from scratch typically gave me a flight response.  I think working it out on paper first, like is typically asked of us in the project, helps a lot.  Must submit next time.
 +
 +====UNIX====
 +This week in UNIX we continued to increase our knowledge of basic but useful command line terms for catting and grepping.  We even took at look at seding.  It was part review, and then moving forward, on things like finding words with no lower case vowels by typing cat words | grep '^[^aeiouy]*$' This goes from the start of the line to the end of the line, making sure that aeiouy are not any of the included, with the * being 0 or more of the previous (or not of).  Another good example was to find all the words with the start and end with a vowel, that are 2 or more words.  We did this by using cat words | grep '^[aeiouy]$.*[aeiouy]$' Again this looks for words that at the start(^) have a lower case vowel, are at least two letters(.*), and end($) with a lower case vowel.  The project we have this week is an extension from last weeks, working with the calendar and figuring out what semester it is based on the week given.  This I will begin working on shortly, days before it's due, as is customary of my people.  We trans procrastinatory people can't help it, and any nay sayers will be abruptly reminded to check their privileged on twitter as such.
 +
 +====Week 11====
 +====C Prog====
 +So this is it, this is what it all comes down to.  This week we finished off more in the bag of tricks, basically just trying to finalize things we've done and adding on a few other things for scripting/C++.  It seems like students and staff alike are ready for it to be over, so to be honest it's harder to pinpoint what we did each day.  The last project was a nice one to go on vacation to, and I finished beforehand to load up on bonus points which will hopefully alleviate some of the previous screw ups in terms of points.  My brain is mush and this final experience project things will probably be the downfall of it into an even more pureed form.  Overall it's been a good semester, I think we learned the majority of what we were meant to.  I dread to think of what I'll have to attempt to recall from the weeks prior the break...  Oh well it will all be over soon?
 +
 +====UNIX====
 +Same thing as above, blah blah blah everything is almost over and very few people are operating on anything other than sheer forceful will.  I feel I've learned quite a bit over this course, and it's a much different setting than C.  It's less piece a, apply in project b, piece c, apply in piece d.  Not to say all of C was that way, there was a lot of go find stuff in the manual or google yourself moments, but UNIX seemed to have way more here's piece a, now do project theta.  It took a bit more collaboration and abstract thought to accomplish the goals.  Hopefully the final experience project will be just as thrilling, though I fear I'll miss the grade school html coding adventure.  I am curious as to if we could pluck students from another college in the same / similar programs and see how they've learned and applied their knowledge vs ours.  These next two weeks will probably fly by, aside from the few hours of bashing my head against the keyboard while trying to complete the final project.  Soon we'll be back to mindless self indulgences and not having to put on pants for hopefully days on end.
 +
 +====Week 12====
 +====C Prog====
 +So this week we were introduced to our End of Course Experience and FUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUU
 +
 +====UNIX====
 +UUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUnnily enough I'll need to put a **lot** of time into it.  19 credit hours didn't seem so bad until now, when everything is being piled on.  It makes me wish we started in early August and finished finals the week before the Thanksgiving break.  I assume they keep summer the length it is to allow for summer classes and to reduce the amount of time students can forget things from fall to spring... but who knows with how these systems work, assuming there is a logical explanation.  If only we could be graded on everything before the break in UNIX... yea, that'd be good.  It's nice to know students aren't the only ones struggling to stay on topic and focus'd though.
blog/fall2015/dm016807/journal.1446498660.txt.gz · Last modified: 2015/11/02 21:11 by dm016807