Faith Thomas

I can't believe I've made it. When I saw Hw01 the first time I was so convinced there was no way I was going to survive this class. And yet, after every assignment thus far I have felt so accomplished and honestly proud of myself. It is easy to doubt yourself when there is a big challenge in front of you, but finishing it is such a relief and like Dr. C says, definitely a victory. Looking back at where I started from where I am now I can say that I've definitely stressed more, lol...but i've also learned a lot! I've gotten more comfortable using IntelliJ, and surprisingly android studio. The first time I saw android studio I was like, "No way, absolutely not", but now that I've worked on it more it doesn't feel too alien to me. I've gotten more comfortable with working with multiple files, with understanding polymorphism, and with remembering to write my javadoc comments. Working with a team for project 2 has been good for me as I haven't d...

Who did you work with? I worked with Sami Hobson and Luis Valadez. What was your strategy for solving the Markov assignment?  Did you start writing code right away? Did you plan it out on paper?  My strategy:  For this assignment, I started by looking at the UML diagram and used it to guide how I set up my class. I began with the constructor and declared all the required fields so the overall structure was in place. After that, I didn’t follow the exact order of the method list in the project file. Instead, I built the methods based on how they were connected. If one method called another, I made sure to write the called method first. I focused on building the most independent methods first—the ones that didn’t rely on any others—and then moved on to the ones that used them. This approach helped me test things step by step and made it easier to build the more complex parts of the program later on. What was THEIR strategy for solving the Markov assignment? Luis's strategy:...

With whom did you work? I worked with Sami Hobson and Luis Valadez.  What was your strategy for solving the assignments?  Did you start writing code right away? Did you plan it out on paper?  My strategy was to start with one file at a time. I started monster.java first and explicitly followed the UML diagram for instantiating the variables and fields and methods. Before building the chunky methods I created 4 other branches, each with an individual monster in it, ex: electricRat, flowerDino, etc. Once I finished building my concrete implementations, I was able to build the chunky methods in monster.java without getting errors saying my electricRat or other monsters didn't exist. I don't like red errors lol. After building my chunky methods in monster.java I had to do a lot of debugging. I ran my tests and a lot of them passed but had some things I needed to fix. Got that done, everything ran smoothly, just happy to be done with it! What was THEIR strategy for solving the...

What improvements would you make to your code/what was suggested?  It was suggested to me to follow the TODO tools in IntelliJ that way I don't get lost in what I need to do next in a large body of code. My Hangman constructor was not done because of this, I didn't catch it but my code still ran so i'm not sure how that happened.  Which unit tests were the hardest to pass? checkChooseWord() and hintTest() were the hardest for me to pass. checkChooseWord() was the first one I started working on so it felt like the most challenging to get started. HintTest() kept bugging out because I couldn't figure out that I needed the floorDiv function in my method. How do the existing tests function and could they be improved? I think they were perfectly fine. I didn't see any necessary improvements.  Do the existing unit tests cover the full range of the sub classes? Yes, I think they covered everything. i went through each test one by one to see what methods they were calling a...

At the beginning of each week, looking at the modules and everything I needed to get done was quite overwhelming, but I got it done. Sometimes it is a surprise when you get your code to run. I would be crying, change something in my code not even knowing if it's gonna work, about to give up, then boom, a little green checkmark tells me not all hope is lost. It's pretty crazy. I've never used GitHub before this class so picking that up definitely gave me a run for my money. Dr.C's videos were a blessing, thank goodness for a pause a rewind button is all I have to say about that. Lab 00 was the first time I've ever used a git command, so that was interesting. Definitely would come in handy if I could get a grip on them. I found the terminal to be able to do some handy dandy tricks that would be useful for the future: git status, git add ., git commit -m (commit message), git push origin (name of branch), these were cool to use. Then I found out there were buttons for ...