Week 01 in Computer Science: Aha!


Greetings All! My name is Brandon and welcome to the blog! This is the first of many posts as I document my computer science journey. I want this blog to serve as a place of reflection and an archive of my learning process (and the cool interesting stuff along the way). So often, I find myself stuck and feeling defeated whenever I encounter a difficult coding problem. But then I realized, this feeling is what makes programming fun. Getting stuck and unstuck; finding the beauty in that "Aha!" moment. Those moments we dread, provide a contrast weight to the moments where we succeed. Can you imagine just always getting everything right the first time? Being humbled by syntax errors, spaghetti code, and excess print statements are the hallmarks of someone learning. We all started as bad programmers, let's not compare our Chapter 1 with another person's Chapter 31 on their spicy take on dynamic programming. It's not about the destination, it's about loving the journey. 


                                                                                    The First week

Prime Solutions Collective resume 
    Week one was filled to the brim with information. This was the first time where we met with our teams and discussed optimal meet times and good practices. We learned to establish a system of accountability and strong communication. Our first assignment turned out to be a success! In our first assignment, we needed to provide a team resume and design a business with our skills. Here is a screenshot of the first page of the design. 

    With my favorite assignment aside, there was a lot of housekeeping and class infrastructure information to soak in.  Our program also allowed us to dive deep in the history of CSUMB. 

    The biggest assignment that was we are currently working on is the Industry Analysis paper. Essentially it is paper that allows us the better understand the job market we would like to enter. The purpose of this paper is arm us with the knowledge of the career we want to enter. One industry that has me completely interested is the embedded systems of Medical Devices. I just find it so facinating how these tiny devices work yet live on or inside of your body!

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