Computer Science BS Journal: Week 11

 

Wk03 Learning Journal: Project 1 Code Review



    This week we are trading our code with our peers and reviewing them to help each other notice mistakes in our code and perhaps improve each others skillset and knowledge. I worked with Neng Lao in the code review, more like he assisted me with some troubleshooting on the assignment. Turns out I make some very sneaky typos every so often that breaks everything. Lol. I'll go over the assignment prompt and answer each question below.

    • Summarize the feedback you received about your code from your peers
      • Some of the feedback I got was to stick to the prompt. I have a bit of previous java experience so I tend to try and use some of that knowledge. For instance I was trying to use append and StringBuilder in some of my code when we hadn't been "taught" that yet in the class. Sticking to what has been taught thus far to hone THOSE skills is something I should focus on. And I agree with that assessment. I'm going to try and refrain from coding in a way that doesn't align with the classes curriculum.
    • Identify any trends you noticed when evaluating the code of others
      • One thing I noticed when evaluating my peers code is that they make good use of comments in their code to explain what everything is doing. I have a bad habit of tunnel vision coding and not putting in those comments. I go back afterwards and add them. But if I add them as I'm coding if I run into trouble I can see what exactly each method is doing so it might assist with troubleshooting.
    • Was any part of the code a struggle for YOU?
      • I'd say troubleshooting is and was the biggest struggle for me. In Project 1 I spent 2-3 hours debugging. I always tend to miss something and reading the problem/error reports is something I need to work on. I'm slowly figuring out how to pinpoint what's throwing errors and use the mouseovers in IntelliJ for reports on what might be wrong/what could be done to fix the errors.
    • Was any part of writing the code easy for YOU?
      • I think writing out the methods and implementing them (for the most part) was the easy part for me, but it was also my biggest victory.
    • What is your biggest victory?
      • My biggest victory in project one I think had to of been creating all of my methods quickly and efficiently. Seems like a small victory I know, but for me it's a big improvement because I tend to spend too long looking at and reading the prompt or code along video that the professor has posted. Jumping right in and coding the methods on my own was a morale boost. We won't speak about the failed tests.

Comments

Popular posts from this blog

Computer Science BS Journal: Week 4

Computer Science BS Journal (CST363) : Week 7

Computer Science BS Journal (CST363) : Week 2