Week 25: CST 334 - Operating Systems

WK01: First Week of Operating Systems

This week introduced several foundational topics in operating systems and computer architecture. The main topics covered were: installation of Docker, introduction to operating systems, computer architecture review, Linux and the shell, programming in C, command line introduction, and a math addendum about binary and hexadecimal conversions.

Starting with Introduction to Operating Systems, I learned what an OS is and how it manages hardware and software resources, providing a bridge between users and machines. This topic was fairly easy to grasp because it dealt with general concepts and functions like process management and memory control. The Computer Architecture Review helped connect how components like the CPU, buses, and memory hierarchy work together. Although interesting, it required memorization - especially understanding RAM layout and how data flows between components.

The Linux and the Shell section felt intuitive and enjoyable, especially the historical connection between GNU and Linux. I've used Linux before, so the explanation about its open-source nature and design philosophy made sense. The Command Line Introduction also seemed simple at first but I realized how powerful it actually is - especially when considering advanced concepts like redirection and piping, which were only briefly mentioned.

Programming in C was familiar territory for me, but I know it will take effort to recall all the useful functions and best practices. The Math Addendum was my "aha" moment - it involved straightforward conversions between binary and hexadecimal, which I find very logical once I use a reference table.

The hardest and brand new topic for me was Docker. I understand it's a virtual container platform that isolates environments, but I don't yet clearly understand its workflow or how it operates internally. I'd appreciate a dedicated lecture explaining how Docker images, containers, and virtualization layers work together.

Overall, this week connected many previous concepts from other classes. I value the review and look forward to learning more about Docker and virtualization in greater depth next. 

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 2. Class: CST 300 - Major Pro Seminar

Image
  Part 1: Review and Reflect Learning Strategy After reading Learning Strategy, I can say that my top 3 items that I am good at are: Creating and Following a Study Schedule: I habitually block out study time in my calendar, which keeps me on track and prevents the possibility of being late. Choosing a Distraction-Free Environment: I’ve set up my work desk specifically for studying - it's a quiet and comfortable space where I can focus. Everything I need is within reach and neatly organized, which helps me stay on task and avoid unnecessary distractions. Active Reading with SQ3R: Before diving into a chapter, I survey headings, turn them into questions, and then read to answer them. That helps me retain key concepts. Here are the top 3 items that I need to improve:  Tendency to Cram When Tired: I sometimes push into late-night review sessions when I'm already exhausted, which makes studying inefficient and causes stress levels to spike. Inconsistent Note Organization: Although ...
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