Week 4


Work with some of your fellow classmates and go through your solution to project 1: LDPM

  1. You can work with up to three people (you MUST work with at least one other person)
    1. With whom did you work?
      I worked with Serena Ngo and Chanroop Randhawa.

  2. What was your strategy for solving the assignments?
    1. Did you start writing code right away? Did you plan it out on paper?
      I started as soon as I could. I always write code out on paper to visualize it.

  3. What was THEIR strategy for solving the assignments
    Chanroop -     Her project strategy involved thoroughly reviewing documents and then working file by file, finishing with Monster.java. She planned her code using rough UML diagrams on paper. 

    Serena - Her approach involved first outlining variables, methods, and classes from the document, then adding JavaDoc comments as guidance. She then went method by method, writing pseudocode and comments, followed by a rough code draft. 

  4. How would you change your strategy having worked on the assignment?
    I would have started earlier and perhaps tried to contact the TA/the professor since i had some problems I couldn't fix, which ended up costing me many points.

  5. According to your classmate(s): how well does your code follow the Google Java Style GuideLinks to an external site.?
    Pretty well!
    1. Did you know you can automate applying some of the style guide rulesLinks to an external site.?


  6. What was the most challenging part?
    I couldn't get the unit tests to work with my code. So I had to change the unit tests, which we were not supposed to do.

  7. What was the most interesting? Perhaps making the monsters and implementing everything we've learnt so far.

  8. What are you the most proud of? Actually being able to complete 90% of the work.

  9. How did you celebrate completing the assignment? 
    1. If you didn't how will you celebrate?
      1. Lots of sleep!!

 


Comments

Post a Comment

Popular posts from this blog

Week 1

Tackling Coding Bat challenges has been a real journey for me, and I've definitely refined my approach along the way. My first step is always to really understand the problem. I don't just skim; I read the description several times and then spend a good chunk of time analyzing the examples. Walking through them manually helps me solidify exactly what's expected. Once I feel like I grasp the core idea, I move on to planning.  When it comes to  implementing the code , I take an incremental approach. I'll get the basic logic working first, then gradually layer in the solutions for those trickier edge cases. I also make a conscious effort to use clear, descriptive variable names. For testing and debugging, I rely heavily on print statements. If my code fails a test, I'll flood it with print statements to see the values of variables at different points and trace the execution. This, combined with carefully reading Coding Bat's error messages, usually points me right ...
Read more

Week 2

This week, I focused on core software development concepts from Lab 00 and Lab 01: unit tests , Git commands , and interfaces . Lab 00 introduced me to writing focused unit tests to verify code components, a practice I see as vital for reliable software. I also began learning essential Git commands like add , commit , and push , understanding their role in version control and collaboration. In Lab 01, I got an early look at interfaces . I learned they define a contract, outlining methods a class must implement. This concept, though new, already suggests how interfaces promote code abstraction, flexibility, and modularity. The biggest challenge was grasping the Git workflow , especially minor merge conflicts. However, the immediate positive feedback from passing unit tests was a great motivator. Moving forward, a strong understanding of Git is clearly crucial, and the initial exposure to interfaces has already begun shaping my approach to designing reusable and extensible code.
Read more