Wk04: Learning Journal Project 1 review

 

Brandon’s Responses

  1. With whom did you work?

            I worked with my Team! (Aida, Analiza, Aohua, & Myself)
       2. What was your strategy for solving the assignments?

My main strategy was to constantly look at the UML diagram. As long as these key pieces were working, then it would serve as the foundation for my project. After all pieces were implemented, I used the testing file to see where my code was not functioning. The testing feature really helped me understand where my code was breaking. 

  1. Did you start writing code right away? Did you plan it out on paper? 

In hindsight, I thinking that writing code right away was a bad idea. I got very hyper fixated on the red underlines that intellij was giving me. I constantly lost sight of what my method was trying to accomplish and what other methods it was interacting with. 

  1. What was THEIR strategy for solving the assignments?

                         Most of their answers resonated with mine. They looked at the prompt and used                         it as a guide. The prompt provide the structure for the entire assignment, and it                            was more on us to figure out how everything worked together.


  1. How would you change your strategy having worked on the assignment?

Read the documentation and try to really understand what each method was trying to accomplish. Even though I was able to satisfy the evil IDE with proper return statements and syntax, my code was still poop (just syntactically correct poop).

  1. According to your classmate(s): how well does your code follow the Google Java Style Guide?

                                 

A.B. Response:

Brandon Evangelista – Your code closely follows the style guide. I suggest adding dates and maybe a short summary for each file just so it’s like a little intro to the entire class.


  1. What was the most challenging part?

Not planning appropriately. 

I was going through alot of life events, and I learned the hard way that it is important to                 plan for these kind of things. Give myself some sort of insurance or cushion as the                         deadline gets closer and closer. 

  1. What was the most interesting?

The context was the best part. Being 1st gen pokemon lover. All the references got me to laugh. 

  1. What are you the most proud of?

I am most proud of it being able to run.  Despite the never ending nested “if- else                          statements” my code child ran!

  1. How did you celebrate completing the assignment? If you didn't how will you celebrate? 

I played pokemon with my kids. I told them I made a bootleg monster game. They                         wanted to see it and were very unimpressed by the graphics. 

Comments

Post a Comment

Popular posts from this blog

Journal week 6

 One of the most interesting sections from this week was the topic of semaphores as a synchronization primitive.  Semaphores serve as way to help manage concurrency and work very similarly to locks but rather than just letting one thread access critical sections. Semaphores can allow “n” number of threads through. But by setting s semaphore to a value of 1, it can act just like a binary lock. As threads pass through a semaphore, a counter goes ups and down depending on what integer was initialized. As threads use the semaphore, the value decrements and once it reaches 0, no more threads can make use of the critical section. Once a counter reaches zero, it does the “wait()” operation. As threads finish with the critical section, it lets go of the semaphore and increments the value, allowing another thread to make use of its resources. It can serve as great synchronization tool, when two semaphores are used in tandem.  Another synchronization primitive we learned about was ...
Read more

Journal Entry Week 2

 One of the most interesting things I learned this week was about CPU scheduling. Everyday I use my phones or laptop, I take for granted the amount of processing power that is being the machine! This week the most tedious thing we did was hand calculate turn around time and response time. We also had to assume that there was only one available core, as other resources were not factored into the calculation.  Among the different kinds of scheduling , each of them have their own strengths and weaknesses. For example the Round- Robin scheduling excels at response time but sacrifices turnaround time in the process. By frequently switching to different jobs in small slices, the computer is able to work on all jobs what seems like simultaneously. With responses times at basically zero,  the amount of context switching that the computer has to do may drastically increase the turn around time.  Another scheduling algorithm we applied this week was the shortest Job priority. ...
Read more

CST334 Operating Systems Week 1

This week was kind of an eye opener. Being raised in an era where the internet just started booming, I always saw a computer as a black box. Almost like a modern-day Ouija board; I use the letters on a magic board and I get to see and speak to another person not in the room.  The internet has become the culmination, and as a teenager I used that knowledge to download sketchy mp3 files off a green citrus application.   I never really thought about computers and how an operating system served as an API. As I my make my way through these computer science course, I now see that I stand on the shoulders of giants. I’ve grown a deeper appreciation for all groundwork laid before me. Breaking down everything that an operating system does for the user is incredible. By the use of virtualization, it almost seems like how flawless using a computer uses its resources. From the users perspective, you kind of just expect it work out of the box.  Another Idea that I take for gr...
Read more