CST300 - Final Videos

Group 8: Otter Consultants
Cody Hopkins, Ysabelle Kim

Drones: Friend or Foe?

Comments

Post a Comment

Popular posts from this blog

CST300 - Week 4

Week 4 has been busy! I have gotten work done a lot later than I would have liked. Part 1: Education Goals My educational goals would be to expand my knowledge about Javascript. The most tangible project to put this in practice would be to create a simple interactable website, possibly using React as a frontend. One of my ideas for a capstone project would be to create a website for a tabletop game I am developing, so the practice would be great for it.   The first step would be to learn about networking -- CST311: Intro to Computer Networking and CST336: Internet Programming would be where I hone these skills. Before these classes, I would like to create a single-task web app as a practice. It would have a starting list of about 20 items, and allow the user to arrange them into 6 specific item slots, like a digital pin board. Then, once I am in these classes, I will look back at this project and see what I can do differently or what I have learned since then.   My web develop...
Read more

CST334 - Week 6

Week 6 Reflection This week, we learned more about semaphores, and the bugs that are commonly faced in concurrency, such as deadlocks.  Semaphores are a synchronization primitive that has a modifiable integer value. The behavior of the semaphore is determined by this value. They can be used as both locks and condition variables for concurrency.  sem_wait() and sem_post() are used to interact with a semaphore. sem_wait() waits for a condition to be met, while sem_post() increments the value of the semaphore, then wakes a waiting thread. If a semaphore's value is negative, this number is equal to the number of waiting threads. For example, -4 equals four waiting threads, incrementing by 1 will change it to -3, waking one thread and now resulting in three waiting threads. Concurrency creates bugs that are difficult or costly to fix correctly. Non-deadlock bugs include atomicity violations and order violations. Atomicity violations occur when instructions that sho...
Read more

CST338 - Week 13

CST338 Week 4 - Project 1 Review Meeting Time: July 18, 2025, 6pm - 7pm Participants: me, Stan      My strategy for solving the assignments was to first get all of the code instructions implemented. I also write javadocs at the same time as implementing methods, so sometimes they can be outdated if the method is changed later. Once that was done, then I could attempt to debug the issues that were present. I did it this way because to test some methods, other methods must be implemented first, so this helps solve that issue. I did not plan it out on paper, since the code instructions were clear enough for me to understand how to implement the methods as asked (at least, 90% of the time).     Stan's strategy is to create the structure of the project first, like the constructors, method and field names, then to follow the code instructions and implement them. After this he tests his code and makes fixes when needed. He uses breakpoints when debugging to check varia...
Read more