Week 04


Part One: Set Your Educational Goals
After going through all the readings of this module, set and write down your educational goal(s) in the CS program (and beyond if you'd like).  The goal should be vivid enough that you can envision yourself achieving it. The goal should be exciting enough that you feel driven to reach it. Your goal should also be specific so you can see how close you are to attaining it, and it should be short/simple enough so you can remember it.
    My current goal is to break into tech as a software engineer ideally in the medical field. I feel that having impact for the end user gives a different kind of satisfaction. Creating something that has form and function. Starting off, programming will be my biggest hurdle. Then I want to move into Embedded systems! They are different beasts that require more specialized firmware tailored to even more specialized hardware! As an Embedded engineer, my mantra will be take straight from a Daft Punk song “Work it harder, make it better, Do it faster, makes us stronger” 


Part Two: Set Your Career Goals
After going through all the readings of this module, set and write down your career goal(s).  It might not be easy, therefore don't spend too much time on it. However, do push yourself to envision the goal, and don't worry if the goal is too grandiose or too modest.
The goal should be vivid enough that you can envision yourself achieving it. The goal should be exciting enough that you feel driven to reach it. The goal should also be short/simple enough so you can remember it. 
    • One line at a time
    o As obvious as it may seem. Becoming a good programmer means practicing a little bit everyday. I need to learn to be okay with the code I produce and not think to hard. Iterating on my ability to write and thinkg critically is the important thing to practice.
    • Improve Soft skills
    o I can be as technical as I want, but if I can’t communicate what I am trying to accomplish my talent doesn’t mean diddly squat. It doesn’t have to be over programming, but try to connect with people and get good at finding common ground.
    • Documenting
    o Showing off a command line tic-tac-toe may not be that impressive. But it is important to take pride in my work. Regardless how big or small a project is, I should take time to reflect and refine the things I put out into the world. 


Part Three: Take a wild guess of your percentile of the ETS Computer Science test
After viewing the ETS page, the test description, and sample test, how do you feel about taking the test in 18 months?  What percentile do you feel you will get, why?
In my current state, I feel that I will score in the 60th percentile. Computer Science concepts are quite difficult and for a lot of the material, I haven’t really got the opportunity to apply it to my projects. But give me 3-4 weeks of studying, I believe that I can hit the 80th percentile. It’s not like I haven’t seen these things before, I just need to jot my memory and get some repetitions of some of the questions (how it’s phrased, the format, and the layout)

 
Part Four: Keep Up With Your Learning Journal
Update the learning journal to include what have you learned from this week's readings and activities. 

This week, we got to dive into our argumentative ethics essay. The topic I chose was whether or not we should have the right to hack back after being hacked by an unauthorized user. Our job is to provide a non-biased approach for both stakeholder and figure out their claims. I believe my topic is quite exciting as it challenges our legal system and highlights how poorly written it is for modern technology. 



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