CST 338 Week 3 Learning Journal

During this week I have worked with Jerrick Wallace, Matthew Ross and Dakota Fouch. I got my code reviewed by Jerrick Wallace and Matthew Ross. It was informative to receive feedback as much as giving one. 

Matthew commented that most of my code is well documented and the comments make it easy to read and understand. He also mentioned that my approach to the display method using String builder makes writing the function more efficient than building multiple strings. 

Jerrick suggested that I need to work more on my comments inside the methods so it's a bit easier to understand complex methods. We had an interesting discussion about the sort function and the efficiency of bubble sort. Overall he thinks that the organization of your code is spot on. 

We all had discussion on the most challenging part of the assignment (Histogram) and we agreed that it's the display method. It took the longest to complete and mostly trying to make it match the formatting in the prompt.

For me personally, the assignment has been fun to do, I think the second challenging method I worked on was the sort function since I wanted to make it use only 1 for loop to reduce the time complexity. Additionally, I spend some time to improve the read method so it uses a hash map to store the values and make it more efficient. 

Comments

Post a Comment

Popular posts from this blog

CST 462S - Learning Journal (service learning)

Working with the American Technology Initiative was really fun, informative, and rewarding. I spent most of my time on their volunteer portal, a prototype level app that makes volunteer reporting way easier. The codebase was almost release ready, so I got to dive in, explore its parts, and see how a familiar tech stack scales up for real users. Since the core features were already in place, I focused on user testing: hunting bugs, suggesting little tweaks, and polishing usability. Even though these were small changes, it felt great knowing they’d make a real difference for volunteers. If there’s one thing I’d change, it’d be the length of the service learning project. 25 hours (over eight weeks) barely gives you time to get comfortable with a new codebase. From my experience, you need at least forty hours just to learn the ropes and even more to add substantial features. I’d love to see future SL programs run at least 120 hours (about six months) so you can really dig in. The highlight...
Read more

CST 300 Week 7

Part 1: Arranging our ultimate research video project was a great experience for us as a team. The entire process was smooth, we all agreed with the concepts that were brought forth and maintained a steady vision during the planning phase. We collaborated mostly during our weekly zoom meetings. With different operating systems, we had to use various tools such as iMovie, powerpoint and Final Cut Pro (which is what I used). Looking back on it now though, what I would suggest is having timelines that allow us to finish the project at least a week early so that we can then look at it and try to improve it. However, our team has a strong bond so sharing each other’s ideas into our projects was easy for us. Part 2: I viewed Lera Boroditsky’s TED Talk “How Language Shapes the Way We Think.” The speaker discusses how much influence languages have on our thoughts and perceptions. She gives examples of different ways in which languages can shape reality, affecting even such basic phenomena as s...
Read more