Week 6



Part 1: Help Your Teammates to Develop Capstone Ideas

Using email or during your team meeting, briefly discuss possible capstone ideas with your teammates. Record in your learning journal what you discussed and if any ideas stood out to you. 


Inspired by interview with an industry professional, I was able to present my capstone idea to my team. The Vital Box. With tele doctor visits becoming more and more common.  Doctors and NP require vital signs to make better diagnoses and treatment plans. The down sides of not going into the doctor office/clinic is that a patient may or may not  have a basic medical devices to capture vitals. These devices included: blood pressure cuffs, a thermometer, a pulse oximeter, and a scale. These basic medical devices can help a doctor decide for treatment. My capstone is meant to create a service that can firstly provide the kit to a patient and integrate all the findings into either and API or stand-alone app. The API route allows the information to be distributed to any teledoc service.  

My team members also pitched awesome capstone ideas. One member wanted to create a dietary app, and another wanted to create an app that assisted gardeners by suggesting plant communities based on the size of the lot. 

 

Part 2: Keep Up With Your Learning Journal

Update the learning journal to include what have you learned from this week's activities. You should cover what you have learned from the career guide, and how your team has started working on the final presentation projects.

  Having experience and having a degree is not enough in the tech market. Being able to articulate the skills you have to offer is crucial to landing a job. Improving one’s visibility in the job market keeps you relevant and an appealing candidate. I think the biggest pitfall is not knowing what you want to be. If one is not decisive, this it becomes difficult to sculpt an optimized path for landing the job. 

Our team’s final project is about AI companionship. I never really considered this as topic, but the more I read into it… the more fascinated I become. There are people out there who have emotional or physical relationships with generative AI. There was a movie title “HER”, where it portrays a lonely man who finds romantic companionship with an AI voice. The details are interesting, and it makes me wonder about the future implications of AI and friendship. There are cool things that I am excited about, but there are things that I also fear, such as who is holding on to my romantic data. 


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