CST 334 Week 5

This week I focused on concurrency and how threads operate within a program. In the lab, I worked on a program that demonstrated how using the same variable across multiple threads can lead to issues, such as unexpected behavior and incorrect outputs. This highlighted the challenges of managing shared state in concurrent programming and the importance of addressing these problems effectively. Alongside the lab, I studied thread APIs, locks, and synchronization, which are key tools for controlling thread behavior and preventing issues like race conditions. These concepts helped me understand how to coordinate threads to ensure that programs run smoothly and reliably. Overall, this week gave me a solid understanding of the complexities of concurrency and how to handle them using the right techniques.

Comments

Post a Comment

Popular posts from this blog

CST 462S - Learning Journal (service learning)

Working with the American Technology Initiative was really fun, informative, and rewarding. I spent most of my time on their volunteer portal, a prototype level app that makes volunteer reporting way easier. The codebase was almost release ready, so I got to dive in, explore its parts, and see how a familiar tech stack scales up for real users. Since the core features were already in place, I focused on user testing: hunting bugs, suggesting little tweaks, and polishing usability. Even though these were small changes, it felt great knowing they’d make a real difference for volunteers. If there’s one thing I’d change, it’d be the length of the service learning project. 25 hours (over eight weeks) barely gives you time to get comfortable with a new codebase. From my experience, you need at least forty hours just to learn the ropes and even more to add substantial features. I’d love to see future SL programs run at least 120 hours (about six months) so you can really dig in. The highlight...
Read more

CST 300 Week 7

Part 1: Arranging our ultimate research video project was a great experience for us as a team. The entire process was smooth, we all agreed with the concepts that were brought forth and maintained a steady vision during the planning phase. We collaborated mostly during our weekly zoom meetings. With different operating systems, we had to use various tools such as iMovie, powerpoint and Final Cut Pro (which is what I used). Looking back on it now though, what I would suggest is having timelines that allow us to finish the project at least a week early so that we can then look at it and try to improve it. However, our team has a strong bond so sharing each other’s ideas into our projects was easy for us. Part 2: I viewed Lera Boroditsky’s TED Talk “How Language Shapes the Way We Think.” The speaker discusses how much influence languages have on our thoughts and perceptions. She gives examples of different ways in which languages can shape reality, affecting even such basic phenomena as s...
Read more