Week 14

 Week 14 (4/16-4/22)

The HW1 assignment was fun, I think I'll approach it more calmly, read slower, and not rush it. It is challenging to do so in this class because it moves really fast.

Jotto, Markov, Pocket Monsters, GymLog. All great assignments to understand concepts better. Especially GymLog since it was with Android Studio, which I had never used before.

Two victories: one was understanding GymLog. Being able to watch the videos is one ability, but understanding them and translating them to any Android app is another. I think using outside resources helped me to grasp other concepts better.

Another victory is the Savnac Android App that my team and I are building. I've spent more time on this project than I have on any other. It has been two weeks of working on it every day. And even though our app isn't finished yet, I already see it as a victory to see how far the team has come and how we've overcome obstacles along the way. Hard to believe that this is the last week of class, two months fly!

I think the one thing I've become better at is understanding the Database, entities, DAOs, the repo class and the ViewHolders. This is essential in an app, so I'm glad I've learned about it.

Week 13

 Week 13 (4/2-4/8)

Markov

With whom did you work? Wootark Kim and Michael Sorensen 

What was your strategy for solving the Markov assignment? Did you start writing code right away? Did you plan it out on paper?

I read the prompting a few times and analyzed the logic data structures and line-by-line implementing methods. I did not start writing code right away. I used sticky notes for methods() names, types, and access modifiers. I read the prompt first, then looked at the UML piece by piece and had it on the side to keep looking at it for the access, types, and names of the methods. I started writing fields, autogenerated constructors, and setters/getters and started working on the most challenging methods first and left the easiest ones to the end.

What was their strategy for solving the Markov assignment? It seemed like they also followed the instructions line by line and added internal comments to their methods to help them not get lost. One teammate followed the lecture/lab video, and the other, with more experience, did it by just reading the prompt and UML.

How would you change your strategy having worked on the assignment? Maybe work on the easiest methods first and then the most challenging ones to the end. It gives room for improvement early on and the ability to leave the frustration to the end and not the beginning.

According to your classmate(s): how well does your code follow the Google Java Style Guide? When I showed them my classes, I didn't have the Javadoc fully developed, so they suggested that I finish the documentation before the submission.

Did you know you can automate applying some of the style guide rules? I learned that while working on this assignment.