CST 334 - Week 2

-

 This week was all about process and process states.  The OS controls and schedules which processes will be run and when.  One way of scheduling processes is the first in, first out (FIFO) method.  To me personally, this method makes the most sense.  The first process started should be the first one to complete but that is not always the case.  Imagine if the first process took double or even triple the time it takes for the processes to start after it.  Another way of scheduling is to complete multiple processes using the Round Robbin method that runs each process for a specific time and then switches to the next.  This process is repeated until the processes are completed.  This can be beneficial for very short processes but as the process becomes larger, the turnaround becomes much longer.  These are just two of many methods of scheduling and as you can see they both have their pros and cons.

We also had some more hands-on practice with the command line.  This time was creating our first C program.  The purpose of this program was to introduce the fork method as well as how parent and child processes are run.  The program took a command line argument (time in milliseconds) when executing to show a delay between a parent and child process output.  We also created a makefile that compiled our two programs using the gcc compiler and sent the output to a file.

Comments

Post a Comment

Popular posts from this blog

CST 499 - Week 10

-
This week I was troubleshooting an issue that arose from the previous week's work.  The layout of the page was affected forcing all of the content to the bottom of the page rather than the top.  This was fixed by implementing CSS directly into the div tag as I did not want to change any of the global CSS files.  Next, I plan on looking through the issues page and selecting some bugs/features to implement.  I did not face any challenges this week, mostly trial and error until I solved the issue.
Read more

CST 438 - Week 7

-
 The Agile and Plan and Document (Waterfall) processes are very different.  In the Agile process, iterations or sprints are used to complete smaller tasks rapidly whereas the Waterfall process follows a predetermined timeline for deliveries.  The Waterfall process is usually used for very large projects and takes much longer due to each delivery being reliant on the previous one.  Also Waterfall process uses a large chunk of time to rigorously plan everything at the beginning of the process whereas Agile allows for changes throughout the process because of the smaller deliveries each sprint.  This allows for quick and simple testing of each delivery versus the Waterfall process that usually begins to test near the end of the final deliveries because again each delivery relies on resources from the previous.
Read more

CST 438 - Week 3

-
  How does React compare to other frameworks you have used for front end development?  I have not had much experience with front end development frameworks.  I have had little experience with JavaScript and HTML.  One thing I noticed about React that is helpful is the ability to have HTML embedded directly into JavaScript rather than have numerous HTML files and JavaScript files.  This is useful in maintaining readable code and code that is easily navigated.
Read more