Learning Journal

  Who did you work with?  Tim Shaker   What was your strategy for solving the Markov assignment? My Strategy is the same as last time but with at the same time bringing along the few things I learn from my previous projects and peer reviews feed back. I try to read the whole project and understand what is needed. Briefly go over the test cases on what are being tested to understand the functions. When it actually comes to coding I've use my previous strategy of coding methods that doesn't uses any other methods. I code the field type and constructor first then jump to methods. I was able to run the code successfully initially but was giving the wrong output and only 2 test cases pass. That is the time I try to fix the bug 1 by 1. I look for where the bug is by debugging 1 test cases at a time. Stepping through the code and check the output each steps. Once everything is done and all test cases are passing and main is running, I add the javadocs for methods. At this point...

  You can work with up to three people (you MUST work with at least one other person) With whom did you work? I work with Tim Shaker What was your strategy for solving the assignments? Did you start writing code right away? Did you plan it out on paper?  Initially I read the documents of the requirements for the program. I then check the test cases involve within the project. I then started coding the things I can easily understand. I writing the codes of methods that doesn't require any other methods. Once I wrote all the necessary methods and classes needed I check the test cases to see which one fail. I try to solve each bug one at a time until everything passes.  What was THEIR strategy for solving the assignments His strategy was to first read the documentation, then scaffold out out the classes and resolve any syntax errors so that the code would compile. From there, he worked on implementing the logic as it was described in the documentation, focusing on gett...

  Whos code did you review? Tim Shaker The reviews you wrote: Overall Tim's code is clean and easy to read. I didn't see any major and minor issues with his code. The way he wrote code is the conventional way to write code in java. His variables are type and named properly. All the test cases pass, the whole project runs properly and the logical flow is easy to follow along. Summarize the feedback you received about your code from your peers: Overall I received positive feedback from my peers. Had some java doc confusion with one of the methods I wrote since my documentation can be misleading if interpret in a different way. Also pointed out to not forget my TODOS in my code. Identify any trends you noticed when evaluating the code of others such as: everyone struggled with sorting or unit tests that were hard to pass The trends I notice is that my peers pretty much write almost identical as mine (not in a bad way). I guess it is good everyone has the same way of solving some o...

 For week 2 of CST 338 Software design we tackled a lot about git commands, test in java and interfaces. For Git commands I was kind of familiar with it already but I learn more about how to do it in command line. I also learn on how to do it with IntelliJ interface. Whether to use the command line or interface is up to the user but I try to keep the balance in using both so I can retain what I learn and how to do it. We also learn to push everything in a remote repository which is Github. Both the command line and IntelliJ interface has a way to push into remote. I also learn how to complete PR and push everything in main. Also when merging locally, it is preferred to re-base while merging in main. Unit testing is also important when developing programs. As a QA myself, I know how important it is, but my job mostly focus on manually testing software. I learn or got familiar on how to create unit test in Java. This is important to ensure the methods involve in each class are workin...

 For the first week of CST 338 we were mostly taught how to set everything up with InthelliJ and make it compile java language using JDK. We were also instructed on how to set up android studio which we haven't gone much further other than installing it and setting it up for future projects. We were also given task which required us to use Github and learn from the experience. I haven't  code nor do I have experience in coding java but one of the practices that help me was the coding challenges in codingbat.com. The knowledge I have with java is the documentations I read and basic ideas like initiating variable, some few logic flows like if statements and loops, and some basic arithmetic set up. The challenges in codingbat.com is beginner friendly and starts easy and it amplifies the difficulty as user moves a long. I like this method since I get comfortable as I move along. Some of the challenges I've encounter are remembering syntax and methods I can use for certain probl...

  Part 1: Review Other Teams' final video projects  Video 1: https://www.youtube.com/watch?v=EUv2vh-8NFg 1. is the topic well covered?  Yes the topic is well covered. As a person who have no idea or knowledge about the topic, the video is well informative.  2. is the presentation clear? The presentation is clear, the text are easy to read and not convoluted and their voices was clear and understandable.  3. how is the quality of the research? The quality of research is  good enough for a person who has background knowledge in CS but unfamiliar with the topic being talked about. The video explain the topic clearly using the technical terms necessary in CS field. 4. how is the quality of the video production? The video production is clear. It is not fast and not slow just enough speed for readers to read the text and understand what the speaker is saying. There were some part that where the speaker was speaking low but it is nothing critical. 5. is the vi...

  Part One     For our final research video project planning we collaborated through meetings and chats in slack. All the team members in our group are active and constantly giving ideas on how to tackle some process. We also shares some resources or websites where we get information for our research so our sources are almost similar. We all end up using Adobe Express for short video and will do PowerPoint presentation for the long video. For adobe express we are able to work on the project asynchronously in order to avoid blockers and we can focus on our sections. Overall the plan was moving on reasonable space considering we are using a new technology we haven't use before. I wouldn't say the process was smooth but it wasn't rough either. I believe this kind of collaborative projects will have some minor issues since each individual person has their own strength and weakness. It doesn't help that we own have different availability and will have to do our best to commu...