Skip to content

Latest commit

 

History

History
23 lines (17 loc) · 3.15 KB

File metadata and controls

23 lines (17 loc) · 3.15 KB

Feedback on past toolboxes

In general the whole process of the toolboxes was a jumbled mix. It was communicated early on that toolboxes were going to have to be submitted at a certain date, however I think that a lot of people (me included) didn't understand the use of them for future projects until the deadline came. For example, I did the pickling toolbox at the same time as MP4 rather than before because I suddenly had a use for it. However, I didn't do the Evolutionary Algorithms toolbox until after the deadline because my MP5 needed it. I think that communicating that toolboxes can and are useful for projects later in the class would motivate people more in spreading the toolboxes out over the semester rather than cramming it into the weekend before. Perhaps having a set due date for all five toolboxes would force people to do that. At the same time, we are college students so we should be able to do that on our own.

Word Frequency

I found this toolbox to be a good refresher on file handling and list modifications. As I'd done things like this before I didn't really learn anything new. The instructions on what work was expected to be completed and how to scructure the program was very clear.

Unittest

This toolbox was very short, and I don't think I learned a lot. I couldn't really figure out why this method of unittesting was better than the one we covered in class. I later found myself wondering how to use unittests in general to test that classes and methods that manipulate objects were working well. It might be good to have more unittest requirements to complete the toolbox as well as prewritten code that students need to test (as in class objects that need to be tested along with the class methods).

Pickling

This was another short one, but I did learn more. Pickling can be quite useful so it was nice to learn about it. It helped my team for MP4. The instructions were fairly clear, and there was a lot of outside suggested documentation provided.

Web Apps (Flask)

This was one of my favorite toolboxes. This introduced me to a new way of using python and how to use a non-javascript language to do web development. A lot of the outside information (Flas, routers, ports, etc..) are explained within the toolbox instructions which is really helpful. The instructions were clear and there was a lot of support provided while still being challenging to implement.

AI and Algorithms

Toolboxes are supposed to be relatively short assignments so I understand why a lot of the code was prewritten, but I found myself really wanting to write the code myself. Having an example of how to implement a path finding algorithm was helpful and I still learned quite a bit. The assignment forced us to really read and understand what the code was doing so the assignment was structured nicely.

Evolutionary Algorithms

I think that the explanations on how the code is supposed to fit together would have been useful. I had to scratch my head a bit to figure out why I was getting certain bugs and figuring out that I was missing certain things. The concept was really interesting and I definitely learned things, I just wonder if it could have been better structured.