Module 3-2 Reflection

docx

School

Southern New Hampshire University *

*We aren’t endorsed by this school

Course

260

Subject

Computer Science

Date

Feb 20, 2024

Type

docx

Pages

2

Uploaded by UltraCamelMaster345

Report
Raphael Tolentino CS-260 Prof. Lebel 19 Jul 2023 Reflection This week's coding assignment was more challenging than previous ones, mainly because I have always struggled with understanding pointers. Our task was to create the engine behind the Menu options displayed by the main class. We had to implement functions like Append, Prepend, Remove, PrintList, and Search. Fortunately, the Resources Section of the course had a highly detailed video where a professor tackled the exact problems I was facing. Initially, I found it difficult to apply my knowledge of pointers to navigate through the list successfully. Understanding the purpose of memory addresses was elusive until I attempted to solve the Append function. It felt like trying to put an item on an invisible table. The video helped me grasp how pointers reveal this hidden table, but I recognize the need to review pointers thoroughly to handle future challenges independently, without relying on step-by-step guidance.
Let us quickly go over each function: Append adds an item to the list, either at the beginning or the end. Prepend adds an item to the beginning of the list. Remove, as the name suggests, deletes an item from anywhere in the list. PrintList displays the current data in the list, and Search performs what I believe is a binary search for a user-inputted key that matches a node in the list. To make these functions work, I had to understand how to specify the particular node I needed to access and manipulate. For instance, in the Remove function, I had to identify the correct memory address to point to, enabling me to remove the intended item. This process reminded me of the switching operation described in Module 2, where we have to drop one item on the table, switch the item we are holding to another hand, and pick up the added item. Additionally, I made the mistake of not creating pseudocode beforehand, leading to the challenge of translating my logical thoughts into code. Having a coherent format like pseudocode would have made implementation smoother.
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
  • Access to all documents
  • Unlimited textbook solutions
  • 24/7 expert homework help