This week was about learning how the Operating System(OS) manages memory. It was somewhat challenging to understand but I believe I have a basic grasp of how it works. I think one of the important concepts of memory was how the OS virtualizes memory for processes. Each process is given access to memory in such a way that it seems like that process is the only one running. As far as the process is concerned all of the memory is available for it to use. However, the OS does some operations on its side to manage the process' memory access to allow for the sharing of the limited memory among a multitude of processes. This managing of memory by the OS is abstracted away from each process and allows each to run without any real concern as to where the data is physically stored in memory.
For the Markov code review I worked with my teammate Brandon Hoppens. My strategy for the Markov assignment was to first read through the entire prompt and ensure that I had a general idea of what the program was supposed to do. I then worked through the prompt building each method before moving on to the next. I built all of the methods and then ran the test after my initial build. I was able to pass a few of the test and failed others. I then went back to the individual tests I failed and manually debugged them. This was in contrast to how Brandon tackled the prompt as he was implementing the methods as they were needed. He worked to ensure each piece that he added worked with the existing code base. I think I would change my strategy to adopt some of his methods and use an incremental approach. I relied on building the entire program before running the first test, and I can see how on bigger projects this could lead to some frustration. The feedback I received from Brandon was ...
Comments
Post a Comment