Wk07/08

Hangman Reflection

Now that I've continued through the course, I feel much more confident in my earlier reflection on how I would approach the HW01 - Hangman assignment. I would read the prompt at least twice - once for familiarity and once to take down any notes and starting points. This will likely become much more apparent when I open the test file, reviewing it at least twice - once for familiarity, once for comparison and note taking. Furthering this, I would continue to read through the unit tests, ensuring to consider what methods are being called in the test functions, as they likely reveal which methods should be solidified in order to make the test for that method run as intended. In addition, I would likely begin focus on methods that don't require a call to another method in order to be run (this helps with set up, as these methods are likely the ones to be called within other methods). Along with pseudo-coding out each method, drawing a visual that would help me make connections, and practicing Lists, I would develop more comfort in implementing and operating Generics. After each method, I would create my own tests to ensure each method is working as intended before moving on to the next. 

Victories

• I feel much more comfortable working with IDEs and, while there is still a learning curve, can see myself comfortably continuing to utilize them. 
• I understand how to read a UML pretty comfortably 
• I have a much better understanding of Activites in Android Studio in that they require an xml, a java class file as the remote, and that it needs to be added to the manifest in order to be viewed. 
• I have more familiarity with databases, specifically Room, enough to (roughly) develop my own in Android Studio
• I understand how to extend classes and when
• I'm more familiar with interfaces and abstracts

Wk05 - Markov Evaluation

Who did you work with? Emmanuel Garcia

What was your strategy for solving the Markov assignment? 

    When I began Markov, I started by reviewing the prompt and reading it fully through. From here, I followed the UML and began the initial setup as soon as possible. While reading the prompt, I noted most of the methods called upon other methods. This directed my attention to the methods that are called, but don't call one themselves such as endsWithPunctuation(). To prepare for the rest of the methods, I reviewed JUnit testing, reading test files, and reviewed certain concepts I was weaker on. Unfortunately, some prior system issues held me back from sitting with the lectures as long as I would have liked, though the little review I've done, as well as having worked on the LDPM and Midterm, supported my progression. I did write out the methods and drew out my if statements so I could get a stronger, visual representation of what the method was doing. 

My biggest struggle was working with the HashMap in conjunction with the array. Rather, I couldn't make a mental connection as to how we would fill the array and store it within the HashMap. My second biggest struggle was the toString() method as I didn't fully grasp when to use the StringBuilder until further example and explanation during the evaluation. 

 

What strategy did your classmates use?
    Emmanuel first began by reviewing the test file, reading all the way through so he could see what the tests were looking for within their associated method. Some of the other function calls within the test file gave him a better direction on which methods needed to be completed first, such as getWord() within the addFromFile test method. This suggested that the addFromFile() method needed to be functional in order for getWord() to run as expected. He drew out everything and had a better understanding on how to visually detail what the HashMap would be doing 

 
How would you change your strategy having worked on the assignment? 

    I plan on coding every day for an hour to keep myself exercised on syntax and to learn how to draw out more complicated concepts such as a HashMap. While I did begin it the day it was assigned, I didn't spend every day on it, which may just need to be a necessary thing for me to do. I'm a very visual learner, so watching videos or seeing how the code operates behind the text allows me to work out the issue without looking too long at code. I also intend to utilize Emmanuel's approach by not only reading the test file, but taking note of any method calls that may be required for the test to run. After reading the prompt, if there are topics I'm foggy on, before opening the program, I may write a few practice examples in my terminal for retention purposes, if other practice sources just aren't enough. Small unit testing and seeing immediate output validates my steps enough for me to continue, but admittedly, working with a test file has been an adjustment. Perhaps creating my own test file, one method at a time, might help be better understand test files created by others.  

According to your classmate(s): how well does your code follow the Google Java Style GuideLinks to an external site.?

    My code followed the study guide pretty well and was in alignment with their own understanding, however, my program was incomplete, passing 6/10 tests initially.