CS Online Learning Journal

  CST 338 – Software Design – Wk04 Learning Journal: Markov Code Review Who did you work with? I worked with Kelia Smith. What was your strategy for solving the Markov assignment? My strategy to solve Markov was to thoroughly read the prompt first. After reading, I began by entering the fields. I then added the stubs for the methods so I can get a good idea of what I needed to do. Then I finally got down to coding while keeping the prompt open for clarification. After implementing all methods I ran the test file and revised any areas where the tests failed. I was not able to complete Markov as intended. What was THEIR strategy for solving the Markov assignment? Lia’s strategy is also to read the prompt thoroughly. She then creates a list of tasks she needs to do for the project. For Markov, she added the fields and method stubs. She then followed along with the prompt to implement each method one by one. She then ran the test file to check for errors indicated by the tests

CST 338 – Software Design – Wk03 Learning Journal: Jotto Code Review 1.       Who did you work with? I worked with Kelia Smith. 2.       Summarize the feedback you received about your code. The feedback I received was mostly about using formatting with my print statements instead of using println. I also received some constructive feedback for showPlayerGuesses() method to handle all cases in the prompt. Lastly, I should add some comments throughout my code to make it easier to see the process I’m trying to implement.   3.       What improvements would you make to your code/what was suggested? I would like to use a string builder for showWordList(), showPlayerGuesses(), and do proper formatting for playerGuessScore(). I would also like to add some comments inside the methods to clarify the statements. 4.       Which unit tests were the hardest to pass? I was not able to pass showWordList() because I needed to use a String Builder and getLetterCount() because I could not

CST 338 – Software Design – Week 02 Jotto- This week’s homework assignment was the program called Jotto. It is very similar to Wordle where you must guess a word and the computer lets you know how many letters from your guess are in the word you are trying to guess. The unit tests I had trouble with were the ones for showWordList() and getLetterCount(). I could not get them to pass. I was able to get the method showWordList() to work but it would not pass the test. The method getLetterCount() was more challenging and I was not able to make it work. The part where we must check for duplicate letters because each letter guessed only counts for one letter from the word you are trying to guess is where I struggled the most. I tried using substring() in conjunction with indexOf() but was not able to make it work. I will have to read more into comparing strings to figure out how to compare each character from one string to every character in another string. The quizzes were also a bit

CST 338 – Software Design – Week 01 CodingBat: Coding Bat work was challenging for me because java was one of the first courses I took when I started my computer science journey. I have not used Java since then. The 45 minutes that Java suggested this assignment should take me was the amount of time I used to watch the videos by Nick Parlante. The process I took to solve these problems was relatively straightforward. I read the documentation provided by CodingBat and then started to “throw code at it.” That seemed to work most of the time since the problems can be solved with one loop at most. When my code would not work and I would get stuck, I would go back to read the documentation and watch the videos again. A feature of coding bat that really helped me was the progress table. Even if your code is not correct, as long as it runs, it will let you know where it is wrong. This lets you know exactly where the issue is. This feature was key to finding the correct solution to sever