A few minutes before our exams were distributed, someone joked, "What if the exam is just one long Python project?". They weren't too far off.
We were told ahead of time that the exam would consist only of writing code. What I can absolutely say is that the content of the exam was what I expected. What I did not expect was how we were tested on our understanding of each concept. Our exam surrounded the idea of prime numbers and of course it covered all of the major topics Professor Downing has been stressing since the beginning of the semester. We had to build a class. We had to know how to build an iterator and an iterable. Non-surprisingly, we had to write tests using asserts. However, instead of direct questions asking to "make a list iterator" or "use map/zip", we were given problem statements and had to determine the appropriate usage of each major concept. I'm definitely not complaining with this type of testing, I think it's a learning experience in itself as we gauge our personal understanding of Python and Software Design as a whole.
Another given - it absolutely helped that I prepared a guide sheet ahead of time. As Professor Downing mentioned beforehand, the actual sheet wasn't of much use during the exam compared to the utility of preparing the sheet before the exam.
So the exam wasn't "super fun" but it wasn't "super terrible" either! Now it's just time to wait for the results and get started on Project 3.
Thanks for reading and I'll see y'all next week! :)
Thanks for visiting my blog! Born in Guyana, bred in The Bahamas, and maturing in Texas, it's easy to say that I've had many interesting and unique life experiences. Blogging is my chance to share them!