Week 5 and 6 was better for me than week 4 which was the week my cousin died and I was already feeling better after our cousin was cremated and we put his ashes in a church's place where ashes are put since I don't really know what it's called and it would be wrong to call it a cemetery during week 6.
The new lesson which focused on legal issues, privacy and ethics also piqued my interest more than the previous lesson which also helped on me focusing and paying attention.
The case on Apple vs FBI also was very interesting and the pointing out of the reason why the case was such a big issue and how it is compared to the case of our Supreme Court Judge Corona being impeached.
Learning Log
Sunday, November 6, 2016
INFOSEC Week 3 and 4
I'm not sure what was happening with myself during this period but I vaguely remember not participating much or not being attentive during discussion on the discussion for these two weeks which was focused on operational organizational security. I think the morning of the day when we started the discussion on the new topic was when me who usually woke up early kinda regretted that because I found out that much earlier that a first degree cousin of mine finally died from the cancer he was suffering from.
We already knew the news of him suffering cancer weeks before and me and my siblings weren't hearing if he was getting well or not. Aside from my sister who visited him in hospital, all three of us brothers refused to visit him because we believed that it would make our cousin feel worse when we see him in a weak state. That, aside from me still attending school were reasons the reasons I chose why I didn't make the time to visit our cousin. It wasn't only during INFOSEC where I was affected, I was like that for around a week and when our family went to the church where the body of our cousin was being kept before it would be cremated, I saw that my cousin, who was a guy who was as big as me and maybe even bigger at times, had become so thin. My other cousins told me later on that that was actually better than when he was in the hospital because the body had clothes on and was probably processed before being presented in that fashion since when my cousin was in the hospital, he was so thin that his ribcages was showing through his skin and there were some parts that were even exposed due to the cancer eating through his skin if I remember correctly.
Anyway, I think that was for week 4. The most memorable thing that I remember that happened on week 3 was my group which composed only of Bautista (who isn't attending anymore after attending one or two classes) and me, got additional members because of students who were added to the class late who are compromised of Anino, Cortez and Ginno. There was also one meeting where Doc Manny substituted if I recall properly. That's the most that I remember of week 3 and 4 aside from the due care and due diligence and a bit of parts after that.
Friday, September 30, 2016
INFOSEC Week 1 and 2
Hmmmm.. . Second take on INFOSEC and a very different approach to how it is being taught. While I have nothing against how Prof. Sean teaches, I actually prefer how Prof. Justin teaches more. Having to read a more than 20 pages PDF with multiple possible questions that might show up in a quiz and trying to memorize those aren't really my strong point. It is obvious that I'm actually late in making this learning log though since I made a mental note to myself yesterday to make it and kept putting it off until later. It's good to know how to make a case study from the previous exercise/assignment and while I'm sure the assignment I sent was mostly wrong, I'm still unsure if the last name I put for Archie is correct and I forgot to inquire sir Justin before leaving last time. I'm also unsure if he sent made and sent sir Justin an assignment too since I forgot to contact him because I was cramming in making the assignment. Hopefully he'll be there next meeting so we can talk and discuss about how we'll go about making the midterm requirement
Monday, December 21, 2015
Paging & Segmentation
This is probably the easiest lesson among the ones taught to us by sir Justin. I find it interesting that it's alsmot just like doing matching type and fill in the blanks simultaneously. It's a fresh experience and probably something I'd rather do since it's very easy to answer. It's even to the point that Kenneth sorta gets how it works and isn't having as much a hard time as like the other lessons.
Memory Management MFT MVT
It was interesting to learn about memory management and I agree that Process Scheduling was needed to be learnt before this one. It's very similar to process scheduling and because we learned it first, this lesson was that much easier to understand and execute once the lesson was taught. Worst fit is still a big hassle to do though since it's like you're deliberately making things worse for yourself.
MVT without compaction is also hard to do but most of the time, worst fit is still more of a hassle to do for me. Given a choice, I'd rather do MVT without compaction over worst fit.
MVT without compaction is also hard to do but most of the time, worst fit is still more of a hassle to do for me. Given a choice, I'd rather do MVT without compaction over worst fit.
Process Scheduling Round Robin HRRN
The topic I'm talking about this time is what I think is the hardest algorithm for process scheduling and the most time-consuming algorithm which are Highest Response Ratio Next(HRRN) and Round Robin(RR)
I say HRRN is the hardest and probably the most hassle algorithm to do because it's the only one where you actually have to compute something to determine what process executes. All the other algorithms doesn't require any calculation at all, Round Robin is the most time consuming because of all the ticks that you need to do and on top of that keeping track of the ready queue and the burst time of all the processes. It's especially much more time consuming when the time per tick in Round Robin is low. Making a careless mistake in Round Robin can change what should be a correct answer into a wrong one so sometimes it's best to be careful and keep proper track than regret it afterwards.
I say HRRN is the hardest and probably the most hassle algorithm to do because it's the only one where you actually have to compute something to determine what process executes. All the other algorithms doesn't require any calculation at all, Round Robin is the most time consuming because of all the ticks that you need to do and on top of that keeping track of the ready queue and the burst time of all the processes. It's especially much more time consuming when the time per tick in Round Robin is low. Making a careless mistake in Round Robin can change what should be a correct answer into a wrong one so sometimes it's best to be careful and keep proper track than regret it afterwards.
Process Scheduling First Come First Served & Shortest Job First
So, late posts and hopefully this and all the posts afterwards will still count towards my grade in OPESYS1 since I've obviously overshot the deadline for it but yeah, if not, I'll just post it anyway.
One of the topics we discussed in OPESYS1 this term is process scheduling following different algorithms. First algorithms we discussed and were taught were First Come First Served(FCFS) which, you can garner from its name is pretty straightforward, and Shortest Job First. Shortest Job First(SJF) is actually pretty interesting if you think about it and it's further divided into non-preemptive and preemptive. I say SJF is pretty interesting in that it's actually impossible to implement realistically since as was told multiple times to us by sir Justin, it's a theoretical algorithm and is impossible to happen from a realistic point-of-view since you wouldn't know how long you plan to use a specific process from the start. From what I observed from my classmates and my group-mates, the preemptive version of the SJF is one of the harder algorithms to get the gist of and understand. I think the name is pretty self explanatory though and that sir Justin did a good job of explaining and teaching it. I guess it's just that each person has different learning curves for different things.
If I recall correctly, Davvid was absent for the SJF preemptive lesson so when group-work came, aside from working on our group's paper, I was teaching and explaining bit by bit while working to both him and Kenneth. Well, due to that though I got decent practice for multi-tasking and solving these types of problems as fast and as efficient as I possibly can. I don't blame Kenneth since I understand that there are really just times where you have a hard time understanding a particular subject, as for Davvid, he does what he can and him asking questions and asking to be taught is a good way to better the knowledge that I already know by teaching it to someone else.
One of the topics we discussed in OPESYS1 this term is process scheduling following different algorithms. First algorithms we discussed and were taught were First Come First Served(FCFS) which, you can garner from its name is pretty straightforward, and Shortest Job First. Shortest Job First(SJF) is actually pretty interesting if you think about it and it's further divided into non-preemptive and preemptive. I say SJF is pretty interesting in that it's actually impossible to implement realistically since as was told multiple times to us by sir Justin, it's a theoretical algorithm and is impossible to happen from a realistic point-of-view since you wouldn't know how long you plan to use a specific process from the start. From what I observed from my classmates and my group-mates, the preemptive version of the SJF is one of the harder algorithms to get the gist of and understand. I think the name is pretty self explanatory though and that sir Justin did a good job of explaining and teaching it. I guess it's just that each person has different learning curves for different things.
If I recall correctly, Davvid was absent for the SJF preemptive lesson so when group-work came, aside from working on our group's paper, I was teaching and explaining bit by bit while working to both him and Kenneth. Well, due to that though I got decent practice for multi-tasking and solving these types of problems as fast and as efficient as I possibly can. I don't blame Kenneth since I understand that there are really just times where you have a hard time understanding a particular subject, as for Davvid, he does what he can and him asking questions and asking to be taught is a good way to better the knowledge that I already know by teaching it to someone else.
Subscribe to:
Comments (Atom)