Skip to main content

Week 11 Learning Journal

 Wk03 Learning Journal: Jotto Code Review


For my code review I received feedback from Brandon Hoppens and Maria Imperatrice. The feedback I received consisted of identifying some areas for improvement for my code and some areas where my logic was off. 


I found the code review very helpful and it was refreshing to have another set of eyes go through my code and identify where I may have made some mistakes. If I had to rewrite the code I would incorporate many of the comments and feedback provided. Both Brandon and Maria provided me with additional insight to how to write the code and suggestions on what parts to change to get the program to execute correctly. I had also neglected to fully document my code with Java style comments. In the future I will be more thorough with my comments and make sure that all methods are properly explained.


For me I struggled with getLetterCount, showPlayerGuess and pickWord unit tests. I was unable to get these unit tests to pass. On reflection I think I need to review the unit tests more closely and attempt to practice more test driven development. I feel like if I spend a little more time understanding the tests I will be able to write the appropriate code. 


Overall it was a good learning experience and getting the insight from my group members helped me identify areas for improvement. It is also interesting to see how other people approach the problem, especially because we were all given the same prompt. There were noticeable variations in our code implementations and seeing other solutions helped me understand that there are many different ways to get to the same solution.

Comments

Post a Comment

Popular posts from this blog

CST 363 - Learning Journal Week 7

This week we learned how to implement a different type of database using MongoDB. For our group project this week we changes the SQL code to MongoDB code. Both of these database applications do a fine job of working with data and saving it to a database. I did find that MongoDB seemed more streamlined than working with SQL. With SQL there seemed to be more setup as in creating prepared statements, and then executing queries. With MongoDB it seemed like a good chunk of the code was abstracted away and this made for cleaner looking code at the call site. If I had to choose I would likely go with MongoDB as it seemed more approachable.
Post a Comment
Read more

CST335 Week 7 Journal Entry

 This week I learned about input/output (I/O) devices and their interactions with the operating system (OS). Two types of devices I learned about were block and character devices. Block devices, like hard drives and SSDs, store data in fixed-size blocks and allow random access, making them ideal for large data transfers. Character devices, such as keyboards and mice, handle data streams one character at a time, supporting sequential access. The OS play a crucial role in managing these devices through device drivers that provide a standard interface to interact with the hardware. Performance characteristics of hard drives, such as seek time, rotational latency, and transfer rates, are pivotal in determining overall system efficiency. By calculating transfer rates for different workloads, I learned how disk access patterns significantly impact performance. Additionally, understanding RAID levels provided insights into how redundancy and striping enhance data reliability and performan...
Post a Comment
Read more

CST363 Learning Journal Week 4

 This weeks learning journal prompts are: 1.  Briefly summarize 5 things what you have learned in the course so far.   2. List at least 3 questions you still have about databases. 1. SQL - Learning how to use SQL was great for me. I had never previously used SQL and I found it to be a very approachable and simple programming language. I learned how to perform queries and build tables to organize data in a manner that was accessible and practical.    Entity Relationship Diagrams - These diagrams I found to be very useful in the initial build out of a database and helps create a visual representation of entities, their attributes and relationships. The ERD can also be used to generate the code required in SQL to model the ERD.   Database Design Process - The text and lectures provided some good guidelines on the process to create a database. I learned how to understand the database requirements by speaking with the end users and also the process of analy...
Post a Comment
Read more