CS Online Weekly Updates

  1.      You can work with up to three people (you MUST work with at least one other person) 1.       I worked with Sydney Stalker and Thomas Vandergroen 2.      What was your strategy for solving the assignments? 1.       My strategy was to complete all the stubs and empty methods, then after I do method by method. And if I run into a method calling another, I do that one then return back because I hate red errors.  3.      What was THEIR strategy for solving the assignments My other teammates strategies were to do stubs first in all the classes, then do the methods. (Sydney) And Thomas’s strategy is to do the methods with the least amount of calls first.  4.      How would you change your strategy having worked on the assignment? I do not think I would change the way I did my work. My strategy seemed to work and I like sticking with it....

The feedback I received from my peers was that I did not need to use “this” as much and I had some inconsistent spacing. I also needed to add more comments. When seeing other peoples struggles it seems there was always one or two methods we struggle with. Each person had a different one but none of us were perfect.   A struggle for me was the attackModifier method because I did not read the UML properly. I switched the defending and attacking variable.   I wouldn’t say there was something specifically easy for me, but if I had to I would say taking a UML and writing the blank methods out. I feel as though I know UML symbols well.   My biggest victory would have to be completed the assignment ahead of time and not waiting until the end to complete it. 

This week in CST 334 was more new information to me. We learned about memory management systems and all about memory allocation. All of which is confusing to me. Segmentation divides address space into code stack and heap. Stack memory is automatically compiled by the compiler for local variables and function calls and heap memory needs the programmer to manage it. malloc() and free() are methods in heap memory. malloc() allocates memory on the heap and returns a pointer to the block, while free() deallocates memory. Being careful with our heap memory is vital to programs running properly. We learned about different ways memory is stored, best fit, first fit, next fit. Each of which has its pros and cons like most methods. We also read about Linux utilities like awk, sed, grep, and regex. We also learned about address translation and how virtual addresses are given a physical address in hardware. We also reviewed again processes which is a program that has been copied into memory to th...

This week we learned a ton about the fundamental concepts of operating systems and its processing. I never thought of how CPU’s run but after this week I now do and now know how! We also learned about exec() calls and what happens when they pass or fail, and fork() calls and how the result is the creation of two processes. The first being the parent process, which initiated the fork, and then the second being the child process, which is a copy of the parent but with its own execution flow. We also learned a lot about CPU scheduling. There are many ways such as First in first out, shortest job first, shortest remaining time to completion, and round robin. All of these are kind of self explanatory based on the name, FIFO being first one first, SJF being the shortest one gets done first, but round robin is an average. It kind of goes back and forth between the jobs to get them all done. I always thought the computer just did it in order, and did not know how big of a deal scheduling is an...

This week we learned a lot more on java and worked towards out LDPM and also created the Markov text generator. For the Markov assignment the hardest test for me was the addBadLine Test and the toString test. I still could not get them to complete properly although I am so so close. One space character is messing the whole thing up. An easy one I'd say would be the ends with punctuation test since we just need to know if the word ends in punctuation. I am proud of completing this whole assignment because it is one of the most sophisticated coding assignments I have done in my college career. Although I could not do it perfectly, I am proud. 

CST 338 My process solving in Coding Bat is to do what the question says, in order. I take it one sentence at a time. I did not plan out the questions but rather just throw things at it and hope it sticks. I used the show API button if I was stuck on what I needed to do and did not know the functions I could use. It worked slowly but surely. I don't think there was anything that did not work, everything worked eventually. It just took time. One problem I ran into was Maps. I never learned maps so I had to go over that to do the problems. It was very informational and will be useful in the future. Most problems took 2-4 tries to get correct.

Week 1 This week I learned a lot and was refreshed on past knowledge as well. Learning about Docker and using my Terminal was new to me. I have never used either so now I have another way to do projects. I previously learned C++ at my old school and it is similar to C. It took a bit to refresh my memory but most came back easy. I also refreshed my base conversions as I learned that at my old school as well. The hardest part of this first week was learning how to use my terminal. Changing directories and navigating where I am in my files was confusing, but became easy after attending office hours and learning what each little command does.