Week 4 about Hashtable is a little difficult to understand! I need more exercise and programming for week 4.
Professor Sriram's lectures at first seemed repetitive, but he does a good job of introducing and reinforcing the subject material and he presents worked examples that illustrate an algorithm or data structure very well. Overall, I thought his lectures were very good. The quizzes provide quick feedback on how well you learned what was just taught, although the formula entry questions could do with a little rework (it's not at all clear how to enter formulae). The programming assignments also helped to become familiar with and understand the material presented that week, without requiring sleepless nights to complete them. So why the 1 star rating? ProctorU. ProctorU is awful. It does not work as promised and does not add value. Their intro video implies that all you have to do in order to be ready to take your exam is download the browser plugin and prepare your exam area. Buried deeper, and easy to miss, is the need to allow screen recording. Buried deeper, and easy to miss, is the fact that you need to download LogMeIn. ProctorU says that LogMeIn allows you to connect with your proctor. In truth, LogMeIn allows someone you have never met and cannot see to have total control over your computer. This is appalling. The LogMeIn issue alone would be bad enough, but proctorU failed to work several times during my exam and required long interrupts while the proctorU technicians tried to fix things. They have a cut and paste blame-the-user message that your CPU or connection is inadequate. On my laptop, with my connection, I routinely have two-way full video Zoom calls while simultaneously running Slack, PyCharm, Android Studio and three web browsers with multiple tabs open in each. Yet proctorU says that running one browser with two tabs and LogMeIn and nothing else is more than my laptop can handle. During the interrupts while they try different things to fix their problems, the exam taker does NOT get back any of the time wasted due to proctorU's incompetence. As part of proctorU trying to fix things, they would take over my laptop via LogMeIn and try to reinstall the browser plugin; they would accept the ToS on my behalf without asking me. I think this is unethical. Finally, when I had limped to the end of the exam the "Submit" button was not enabled. I contacted the proctor. She told me to reload the page. The "Submit" button was then enabled, but reloading also wiped out half of my answers and I had to re-enter them. The web is rife with proctorU horror stories. Search on "proctorU, ucsb" and see how proctorU responds to criticism: Not by trying to refute it, but rather by trying to intimidate the critics with threats of litigation and prosecution. I really wanted to pursue the MSDS with CU Boulder, but I don't plan to do so given that they use proctorU. This was a very expensive lesson for me. I will also leave a similar review for 5502 (Trees and Graphs) where my proctorU experience was even worse.
