Week 30: CST 334 - Operating Systems

WK06: Weekly Learning Reflection

This week's material focused heavily on thread synchronization, and I found that the topics connected more tightly than I expected. We covered condition variables, the bounded buffer implementation, the Anderson/Dahlin method for transforming ordinary classes into thread-safe ones, semaphores, and synchronization barriers. Although each topic introduced a new primitive or pattern, they all centered on the challenge of coordinating multiple threads correctly and avoiding issues like races, deadlock, or inconsistent shared state.

In my own words, condition variables provide a way for a thread to sleep until some condition becomes true, while the lock protects shared data the condition depends on. Coding the bounded buffer helped me see why both the lock and the condition variable are essential; without the while loops, spurious wakeups or reordered scheduling would break correctness. The Anderson/Dahlin method made this even more procedural by giving a step-by-step system for adding locks, conditions, waits, and signals to an existing class, something I found surprisingly intuitive because it turns synchronization into a checklist rather than guesswork.

Semaphores, on the other hand, felt more mechanical but also more powerful. They combine mutual exclusion and scheduling control in a single primitive, and the barrier problem showed how they can coordinate groups of threads - not just pairs. The hardest topic this week was distinguishing which synchronization primitive is the right one for a given problem. I understand each tool individually, but I still want more clarity on how to choose between semaphores and condition variables when designing a solution from scratch.

My "aha" moment came from comparing the bounded buffer using condition variables against the same problem solved with semaphores. Seeing two different approaches to the same coordination task helped me understand that the underlying patterns are the same; the differences are mainly in how control is expressed. Going forward, I'm curious how these synchronization techniques extend into larger systems and whether future modules will connect them back to virtual memory, scheduling, or OS structure.

Comments

Post a Comment

Popular posts from this blog

Week 4. Class: CST 300 - Major Pro Seminar

 Part One: Set Your Educational Goals My goal is to graduate from the CS program with a strong understanding of core computer science concepts and score above the national average on the Major Field Test. I want to strengthen my skills in algorithms, systems, and software engineering so I can grow in my current software development role and take on more advanced projects with confidence. Part Two: Set Your Career Goals My career goal is to move into a senior or lead software engineering role within the next few years. I want to become someone my team can rely on for architecture decisions and mentorship. I can picture myself leading major projects, making technical decisions, and helping others grow. Part Three: Take a Wild Guess of Your Percentile I feel reasonably confident about taking the ETS Computer Science test in 18 months. Based on the sample content, I'd probably land around the 75th percentile.  I already have a job in software development, and with continued learni...
Read more

Week 5. Class: CST 300 - Major Pro Seminar

 Part One: Support and Comment on Teammates' Goals My first comment is here and the second one is here . Part Two: Possible Capstone Ideas Three possible capstone projects I might pursue include a web-based incident reporting system, a performance tracking dashboard, and a scheduled report delivery platform. The incident reporting system would allow users to submit, review, and manage incident reports through a secure web interface. The performance tracking dashboard would present key employee or departmental metrics using interactive charts and tables, helping managers analyze trends over time. The report delivery platform would let users configure recurring report schedules and automatically generate and send formatted reports via email. Each project would be built using modern web technologies and structured to support real-time data interaction, role-based access, and reporting capabilities. These ideas would allow for the creation of functional, scalable systems that address r...
Read more

Week 20: CST 363 - Introduction to Database Systems

   WK04:  Midpoint Reflections I'm not new to databases and have some practical experience with SQL, but this course gave me the theoretical backbone for concepts I've used pragmatically. I connected everyday tasks - designing tables, choosing keys, writing joins, and skimming plans - to the relational model and formal normalization. Seeing why clustered vs. heap layouts affect access, how B-tree indexes support equality/range predicates, and where optimizers derive their strategies clarified earlier "rules of thumb." Overall, I gained vocabulary and structure to justify design choices. Brief Summary of 5 Things Learned I strengthened the relational model: entities/attributes, candidate vs. primary keys, and why foreign keys enforce meaning across tables. I practiced expressive SQL beyond basics - joins, subqueries, and aggregates - while reading execution plans to understand scans, seeks, and join algorithms. I deepened constraints and referential integrity to preven...
Read more