Unfortunately, this week the contribution is coming late. My personal scheduler (my brain) was unable to switch efficiently between processes during this week. The task of traveling on the weekend to meet my family took priority and starved all other processes on the queue. There was no First In, First Out algorithm applied, as I began to study last Thursday. Then this also got interrupted by work related tasks by the end of the week, together with the previously mentioned travel.
A smart personal scheduler would have allocated resources to the assignments appropriately, even under a long and time-consuming process such as going to another city. It could have used a Multi-level Feedback Queue (MLFQ) to clearly organize the competing processes and, eventually, run a Round-Robin algorithm to rotate the week assignments in the morning or late at night, when the CPU usage was reduced. This was not fully optimized, as I was only able to cover the reading assignments during the weekend. The result was that the discussion forum assignment went to the end of the queue and no priority boost was applied to level everything from time to time. Such a pity.
Despite the rush at the end, I was glad that no Shortest Job First (SJF) or Shortest Time to Completion First (STCF) was used instead. This could have made me lose the train, or even the dinner with my family. It is not a good idea to simplify too much and lose the context of the processes at hand. There are things that are priority no matter what, and for me family is one of them.
Arpaci-Dusseau, R. & Arpaci-Dusseau, A. (2012). Operating Systems: Three Easy Pieces. Madison, WI: University of Wisconsin-Madison. Available at http://pages.cs.wisc.edu/~remzi/OSTEP//