cst438 - week1

    This week was a nice introduction to the course along with some of the services we'll be using, specifically spring boot. I really enjoyed the labs because they gave me a chance to become familiar with spring boot again and refresh my understanding of its components. It was a good balance of reviewing concepts I had seen before while also preparing me for the rest of the course.

    Before this week, I thought of software engineering primarily as the process of designing and integrating large systems. In my mind, software development was focused on writing the individual pieces of code, while software engineering was about connecting those pieces through APIs, microservices, and overall system architecture. After this week, I still think those ideas are an important part of software engineering, but I've realized that the development workflow is just as important. The processes, tools, and teams use to build software efficiently are a major part of engineering, not just the final system design.

Comments

Post a Comment

Popular posts from this blog

CST334 Week 6

       This week we continued concurrent programming and synchronization concepts and built on the ideas from last week. One of the first things I learned about was binder buffer coding, which was about how data can be shared and communicated between different parts of a system or between different threads. It's a used when dealing with message passing or structured data flow. Systems with modular or layered designs can make use of this to communicate with other parts of the system.    After  that, I learned about the concept of semaphores. Semaphores are a core component in concurrent programming as they act as signaling mechanisms used to control access to shared resources. The main idea of semaphores are integer variables protected by atomic operations like wait() and signal(). A semaphore can be used to limit the number of threads that access a resource such as a database connection pool or a bounded buffer to ensure that the variables remain safe ...
Read more

CST334 Week 7

      This week I explored how computers handle input/output and manage storage at both the hardware and software levels. I started by learning about I/O devices and the role of the bus, which acts as the main pathway for transferring bytes between the CPU, memory, and peripherals. I learned about three primary ways the CPU interacts with I/O are polling, where the CPU repeatedly checks if a device is ready; interrupt driven, where the device signals the CPU when it’s ready, and direct memory access, where data is transferred directly between the device and memory without continuous CPU involvement.      Next I learned more about how physical hard drives work. They store data on spinning metal disks called platters, which are read and written to by specialized heads. I learned how to calculate a drives average rotational delay which is the time it takes for the correct sector to rotate under the read/write head and how that, along with seek time ...
Read more

CST334 Week 3

     This week I learned how memory is organized and managed within a computer system. One of the key concepts I learned about was the address space, which is divided into sections for the code, stack, and heap with each of these sections is designed for a specific purpose. the code section stores the executable instructions, the stack manages function calls and local variables, and the heap is used for dynamically allocated memory at runtime. I found it interesting to see how these areas are laid out in memory and how their addresses are manipulated so programs can run efficiently.      An important reason to structure memory this way is to virtualize it, which helps protect different parts of the program and ensures that memory is used effectively. Virtualization makes sure each process believes it has access to a continuous block of memory, even though the actual physical memory might be shared with other processes. This design both improves security and...
Read more