CST Week 3

 Project 1 review

  • Summarize the feedback you received about your code from your peers
        Code functions and is commented well.
        
  • Identify any trends you noticed when evaluating the code of others
        We all had a pretty smooth time working on the project. Instructions were very clear and easy to understand.

  • Was any part of the code a struggle for YOU?
        No sections caused any struggle.

  • Was any part of writing the code easy for YOU?
        Not necessarily the easiest, but I enjoyed writing the attackModifier() method.

  • What is your biggest victory?
        Staying on top of commenting and keeping comments insightful.
        
  • Who did you work with?
        My teammates; Brandon, Tim, and Lex

  • What improvements would you make to your code/what was suggested?
        Make the attackModifier() method more condensed. I believe while it could be condensed, the way its written makes it easily readable and allows it to be expanded on very easily.

  • Which unit tests were the hardest to pass?
        None. Once everything was built the tests passed without issue.

  • How do the existing tests function and could they be improved?
        There could be an additional test for the takeDamage() method.

  • What did one of your teammates struggle with?
        When to use getter and setter methods.

  • What are you most proud of on your submission for Project 1?
        Building a program that could be easily expanded into a fun little game!

Comments

Post a Comment

Popular posts from this blog

CST300 Week 2: Drafts and Peer Reviews

Image
Part 1. Review and Reflect Learning Strategy      The top 3 effective study skills that I am strong in are Surveying, Making and revising a schedule, and Recite. Anytime I am presented with a new set of coursework I carefully overview the material and create a study plan allocating the time that will be required to cover and review it.      The 3 I am weakest in are Outlining textbooks, Where to study, and reciting. For one, I don't typically mark on textbooks, I also typically study at my computer which can often lead to distraction if I'm not careful, and lastly I can sometimes find myself reading through a section without fully grasping what I just covered.   Part 2: Preview Time Management Skills Part 3: Project Management Basics     The three video presentations, Introduction to Project Management, A WNS Masterclass, and Project Management in Under 5, were all incredible resources in learns key aspects about project management. The ...
Read more

Week 4

  Part One: Set Your Educational Goals     I have always told myself that I want to continuously develop my skills as a developer. There is always more to learn and new avenues to explore. As far as a set in stone goal to achieve, completing my Bachelor's is first and foremost. Once I achieve that I can start focusing on other certifications that may be beneficial to my career. Part Two: Set Your Career Goals      For my career goal, I hope to one day be in the position to design software systems. I enjoy writing code, but its always been building more than just producing that has fascinated me the most. My ideal role would be as a Software Architect. As an architect more of my responsibilities would revolve around developing the overall structure and project design rather than just working on coding tasks.     Even beyond that, it is a dream of mine to open a game development studio. Much of my spare time is spent working on small personal p...
Read more

CST334 Week 2

    This week has been a great introduction to how CPU process selection works in operating systems. We covered a range of scheduling algorithms, including FIFO (First In, First Out), LIFO (Last In, First Out), Shortest Job First (SJF), and Round Robin (RR). I learned how each algorithm has its own strategy for picking which process should run next, and how these choices affect system performance and metrics like response times.      I also learned to calculating those performance metrics such as response time, turnaround time, average arrival time, and average turnaround time. For Round Robin scheduling in particular, I learned how to calculate how long a process will stay in the system based on the time slice and the number of other processes in the queue. These exercises helped me understand the mechanics of how schedulers work and why the design choices made are so important.      One of the most interesting parts was comparing the pros and ...
Read more