-

 

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 that were failing. She continued revising her code until everything became functional.

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

I believe that going forward I would like to keep my current strategy and add Lia’s strategy of making a to-do list of tasks for the project. This will allow me to keep track of what is pending as well as catch anything I have missed. I would also need to adjust how early I start to code. If I start as early as possible, I can get help from our TA or our professor if I get stuck on a particular problem.

According to your classmate(s): how well does your code follow the Google Java Style?

According to my classmate, after going through my code, she could not explicitly see any areas of the style guide I may not have followed. I had the correct import statements, naming conventions of variables, whitespace usage, and have correctly utilized block comments throughout my code.


Comments

Post a Comment

Popular posts from this blog

-
Image
  Week 2- CST-300 Module 2 OLI – Module 2 This week’s module focused on collective intelligence, reading the mind in the eyes, behavior of good teams, and why team skills will help after graduation. Collective intelligence illustrated how teams that have better collaboration skills were more successful. Meaning that everyone participated and contributed to complete the task or project. Some key features of successful teams were equal participation, higher number of women, and social sensitivity. I enjoyed the reading the mind in the eyes activity. It is difficult to tell a person’s emotions by examining just their eyes and not the entire face or body language. I scored about average. I will continue to participate and share my thoughts and ideas on topics being discussed in my team. Behaviors of good teams was a research article done at google looking for the perfect team. They found that teams promote better job satisfaction, better problem solutions and faster innovation.
Read more
-
Image
  Week 1- CST-300 Module 0 & 1 Team Resume Hello and welcome to my first post. This is a screen shot of our team resume. Although we ran into issues with some members missing, we eventually joined with another group and managed to collaborate on this assignment. Our team did an excellent job with their bios and completed the assignment on time. Module 1 Lecture   The readings from module 1 taught me about CSUMB's history and vision statement. It also covered the Degree programs from the School of Computing and Design and its faculty. The lecture also included a video titled "Study Tips to Succeed as an Online Student." The video taught me that I will need to read the syllabus, plan weekly study times, connect with classmates, check canvas frequently, and ask questions to be successful in this class.   Module 1 Lab   The lab for this week explains the American Psychological Association (APA) writing style. APA is the style used by the Computer Science departmen
Read more
-
  Week 3- CST-300 Module 3   OLI – Module 3 This week’s module is titled “What do You Bring to the Team?” and it is made up of six sections. The first section was Processing Styles and Diversity Communication. It explains approaches that would help an internal processor in your team. Some examples were to think silently for a minutes before discussing for answers, ask if members need more time before responding, and use email to communicate. The second section was Work Styles. Here we learned about work styles Get it Right – Task oriented, Get it Done – Task oriented, Get Along – people oriented, and Get Appreciation – People oriented. Each style had its strengths and weaknesses and we had to figure out how to balance them or how to help others with a different style. The third section was Your Booth Team Members. Here we watched a video of each booth member. We were then tasked with ways to support each member’s work style. The fourth section was Conflict Styles. It focuse
Read more