Week 7

  Part One

Reflect on your team's Final Research Video Project Planning.  How did you collaborate?  What tools did you use to communicate and produce? Is the process smooth, what will you do differently next time in large collaborative projects?


After a lot research, our team was able to meet today and assign tasks. Our meeting platform of choice has been google hangouts from the beginning of the 8 week rotation. It allows us to chat, upload files, and host our meetings. Having the whole google suite has really allowed us to collaborate despite being purely digital. 

In terms of content, our team plans to use the wonderful and easy to use platform of Canva. Canvas has wide variety of media options and templates. Poetically, Canva was also the platform used to create our very first group project.  So far everything has been pretty smooth! I think the two biggest hurdles are the time constraint and being close to another big assignment, the ethics paper. The ethics argument paper is required to satisfy the GWAR requirement set by the state of California. Thus, it is understandable that most of our individual time was allocated to the paper. But now with it over, we have about less than a week to create content, record it, and polish and produce both videos. Next time, I think time allocation would be the best thing to focus on. Juggling multiple projects is a part of this intense program, I can now see why there is a lot of focus on time management.

Part Two

Please reflect on the Lecture readings in this section and what you have learned from this week's activities.’

The biggest takeaway for me is that understand the value of presentation skill. Regardless of the technical prowess one may possess, the ability to present and convince stake holders is the hallmark of a great engineer. On top of understanding the power of presentation, I learned how important it is to collaborate. Being able to learn how to give and take and when to be assertive and passive. Knowing when to when not to do all these things are important toward clean execution. 



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