nice

good

good

good

nice

good

good

good

good

good

Cool

ddd

ok

...

ok

g

i

I

S

h

-

I appreciate all who tried their best to make this course, but it just didn't work out for me as well as i wanted. I feel like i didn't retain much information, and that a lot of words and topics were thrown at me so quickly. There were virtually no useful or practical things to do to help us learn hands on either. There were also a lot of things that were not explained properly in depth and that are skimmed over. There are even things mentioned in previous lessons or sections that we don't learn about until much later, but is also glossed over a bit. I dont mean to bash the instructors and the other people behind the scenes who put this together, but at a certain point, i honestly just downloaded the text from the videos to teach myself better. Some videos is someone just reading the text with no prompts or diagrams for 7+ minutes, and videos that have prompts are...almost useless to be honest. I appreciate the attempt at diagrams, but they're not really useful to follow along that much. Anyway, there's more to unpack but my fingers hurt lol. There was some good, like i learned a lot of cool stuff, even tho little portions of the information wasn't useful to my graded quizzes. I hope this course works out for any others that wanna try it. its good to get your feet wet in IT.

I like the part about how tcp/ip works the most. The security stuff was a bit over my head. I worked with printers years ago and used to see issues with laptops that couldn't print quite often. I read online that Jewish vocational service has a program where they say you need google IT and they can get you a job, but the economy isn't so good anymore, so that may no longer be true. I used to fix printers at work for 12 years and occasionally diagnose a bad laptop for IT. Maybe it's beyond the technology, but they need to put a bad pc in front of the students online and tell us the problem , so we can diagnose it. I used to see corrupt operating systems that stopped printing, laptops not getting required updates and extremely slow pcs with full hard drives. They need examples of broken pcs. I even saw a pc that spat out gibberish on startup. The bios on the motherboard was corrupted somehow.

-Not very well structured; probably you could categorize better the topics of weeks 5 and 6. For example, the steps of incident handling are not very clearly differentiated: I assume they are detection, contention, correction, and testing... but I could also set analysis and recovery as separate steps.

-Some topics include too much in-depth information, like different forms of authentication, making it difficult to discriminate important information and technical details. Also, the way they are presented makes difficult to differentiate which of them are intended for authn., for authz. or for both.

-Final project evaluation was disappointing. I spent several days working and researching just to find out that I could had input "lorem ipsum" in the textbox to get approved. I expected some specific feedback or peer reviews like in other courses.